List installed AKA detection packs, versions, and available updates
Scanned 8/31/2026
Install to Claude Code
npx -y skills add akasecurity/ai-tc --skill detections --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Detections?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/akasecurity-detections)More formats (shields.io, HTML) on the badges page.
---
name: aka-detections
description: List installed AKA detection packs, versions, and available updates
---
# AKA detections
Run the read script and show the user its output **exactly as printed**. The
script already prints its content inside a Markdown code fence — reproduce that
verbatim and do **not** add another code fence, strip the fence, or reformat it.
The fence is required: it is a space-aligned monospace table that Markdown would
otherwise collapse. Do not reformat the columns or restate each row.
```bash
node "${PLUGIN_ROOT}/scripts/query.js" detections
```
This lists the detection packs installed in `~/.aka/data/aka.db` — one row per
pack with its installed version, the latest version this plugin ships, rule
count, enabled state, assigned enforcement policy, and whether an update is
available. These packs are what the plugin actually scans with.
Detection updates are **never applied automatically** — a plugin upgrade only
records what's newly available; the installed packs keep running unchanged
until the user updates them. This skill is strictly **read-only**: do not
apply, enable, disable, or re-policy a detection from here. If the user wants
to update, tell them to run one of these themselves in a terminal:
- `aka detections update --all` — update every pack
- `aka detections update <pack-id>` — update one pack
- `aka dashboard` → Detections → **Update** — review and apply in the dashboard
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.