A read-only command that lists recent AKA Security findings from a local database. AKA Security detects possible secrets or other sensitive data, while storing only masked matches.

Use it to review recent detections, their categories, severity, actions, and masked matches, or to inspect only findings at a chosen severity.

It gives you a quick record of what was detected without exposing the original sensitive values. You can narrow the list by severity, such as critical or low.

findings — Command for Claude Code by akasecurity

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add akasecurity/ai-tc

Claude Code

/plugin install aka

Made for: Claude Code.

Or install aka, the plugin that ships this one along with the rest of its 10 commands, 8 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/akasecurity/ai-tc/findings.svg)](https://agentmods.dev/commands/akasecurity/ai-tc/findings)

Your own site

<a href="https://agentmods.dev/commands/akasecurity/ai-tc/findings"><img src="https://agentmods.dev/badge/commands/akasecurity/ai-tc/findings.svg" alt="Measured on agentmods" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 247 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.00247
Opus 5	$0.00005	$0.00123
Sonnet 5	$0.00002	$0.00049
Haiku 4.5	$0.00001	$0.00025

Measured 8d ago against content hash 7d481b43d61f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

findings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/claude-code/commands/findings.md · 24 lines

What it actually says

AKA findings

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.

If the user asked to filter by severity — e.g. --critical, --high, --medium, --low, or --severity <level> — pass that flag through to the script unchanged. Otherwise run it with no flag.

node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" findings [--severity <critical|high|medium|low>]

This lists the most recent findings from ~/.aka/data/aka.db with their rule, category, severity, action taken, and the masked match (raw secrets are never stored), narrowed to one severity when a filter is given. It is read-only.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 24 lines · 11 tokens per session scan A 7d481b43d61f

Subscribe to this mod's changes

findings is a command published in the GitHub repository akasecurity/ai-tc (11 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 247 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Security agents ai claude claude-code-plugin harness-ai

findings

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

AKA findings

What this file has done since we first saw it

Other commands, from other repositories

address

post

show

fleet

optimise

extract-lessons