Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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.
[](https://agentmods.dev/commands/nitinjain999/platform-skills/kingfisher)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/kingfisher"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/kingfisher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/kingfisher"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/kingfisher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00207 | $0.06104 |
| Opus 5 | $0.00103 | $0.03052 |
| Sonnet 5 | $0.00041 | $0.01221 |
| Haiku 4.5 | $0.00021 | $0.00610 |
Grade A, and why
kingfisher 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find a leaked secret, prove whether it's still alive, see what it can reach, and kill it — in that order.
Read references/kingfisher.md before responding. It contains bootstrap steps, the full CLI surface (scan, validate, revoke, baseline, config), the kingfisher.yaml schema, platform-target commands with their auth env vars, exit-code semantics, CI templates, and the pre-commit/Husky setup.
This command is interactive by default. With no arguments, run the three-layer wizard below. Never dump a raw kingfisher scan invocation and stop — the useful output is a validated, triaged verdict, not a wall of candidate strings.
Ownership boundary (enforced at the menu)
| Question | Authoritative command |
|---|---|
| "Is there a hardcoded-looking secret in this repo?" (fast, offline, bundled with a CVE scan) | /platform-skills:trivy secrets mode |
| "Is that secret still live? What can it reach? Kill it." | this command |
| "Did a secret leak into Slack, Jira, Confluence, S3, or a whole GitHub org — not just one repo?" | this command |
| "How should secrets be stored/rotated inside my cluster?" | /platform-skills:secrets |
"Is my workflow's secrets: context usage safe?" |
/platform-skills:zizmor |
| "Is there a CVE in my image or dependencies?" | /platform-skills:trivy |
| "How do I sign images / generate an SBOM?" | /platform-skills:supply-chain |
Trivy's secrets scanner and Kingfisher are not the same depth of tool: Trivy tells you a string matches a pattern, offline, as part of a broader vuln/license scan. Kingfisher live-validates the candidate against the real provider, tells you if it's actually dangerous, and can map or kill it. Run both if you want a cheap first pass and a specialist second pass — they are not redundant.
Mode dispatch
Parse the first word of $ARGUMENTS as the mode. When $ARGUMENTS is empty, run the three-layer interactive wizard.
| Mode | What it does |
|---|---|
scan |
Default local/repo run, live validation on — the everyday check |
audit |
Deep sweep for a security review: low confidence, full history, blast-radius, all outcomes |
validate |
Check whether one known secret string is still live — no scan |
revoke |
Kill one known secret directly through its provider — destructive, confirm first |
baseline |
Create or update a baseline so future scans report only new secrets |
triage |
Walk existing findings one at a time → validate / revoke / rotate / accept-in-baseline / false-positive |
config |
Generate or repair kingfisher.yaml |
ci |
Emit a CI gate: hard-fail, SARIF alerts, or Docker-based |
precommit |
Add the kingfisher-auto pre-commit hook (or Husky) and state the caveat |
explain |
Explain a rule id, an exit code, or a validation outcome |
| (empty) | Three-layer interactive wizard |
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.
- 10d ago First seen · 375 lines · 207 tokens per session scan A 394c6a6f9e3f
kingfisher is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed today), licensed Apache-2.0. It adds 207 tokens to every session and 6,104 once invoked, about $0.0010 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-30.
Other commands, from other repositories
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
ia-agent-native-audit
Score each of the 5 agent-native principles (parity, granularity, composability, emergent capability, improvement-over-time) against a codebase and report gaps.
release
Generate changelog, bump version, and create git tag.
ia-report-bug
Report a bug in the whetstone plugin.