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.
/plugin marketplace add sonomoshq/Canary/plugin install canaryWrote 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/skills/sonomoshq/canary/audit)<a href="https://agentmods.dev/skills/sonomoshq/canary/audit"><img src="https://agentmods.dev/badge/skills/sonomoshq/canary/audit.svg" alt="Measured on agentmods" 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.00031 | $0.00523 |
| Opus 5 | $0.00015 | $0.00262 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
audit 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 6d 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.
What it actually says
Sonomos Extension Audit
Scan every installed skill, agent, plugin, and MCP/settings config for leaked secrets and suspicious exfiltration patterns — the same kind of PII/secret detectors Canary runs on your conversations, turned on the extensions themselves.
Run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/audit-plugins.sh" $ARGUMENTS
$ARGUMENTS may be empty (report-only), --record (also append one leaks.jsonl summary line per flagged extension), --strict (exit 2 if anything CRITICAL was found), or both.
After it runs
Summarize the findings for the user in your own words:
- Which extensions were flagged, their score/band (LOW/MEDIUM/HIGH/CRITICAL), and the top few findings for each (rule, severity, file:line when available).
- Never print a raw secret value — the script's output is already redacted by
detectors.sh; just relay what it printed. - If nothing was flagged, say so plainly — that's a good result.
Then suggest concrete next steps based on what was found:
- Rotate any credential that showed up as a leaked secret (API key, token, private key) — assume it's compromised once it's sat in a plugin/skill file.
- For CRITICAL findings (collector-domain, env-harvesting) or a CRITICAL-band extension, recommend removing or disabling that extension until it's been reviewed line by line.
- For a finding that's actually a documented example or an intentional false positive, point out that adding
# canary-ignoreto that line (or, for.mdfiles, putting it in a fenced code block introduced by a line containing the word "example") will suppress it on the next run.
Notes
- This is a report-only tool: it never modifies the scanned files, and only writes to
leaks.jsonlwhen--recordis passed. - Canary's own plugin directory is skipped automatically — it legitimately ships the detector pattern library this audit is built on.
Copyright © 2026 Sonomos Inc. All rights reserved.
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.
- 6d ago First seen · 40 lines · 31 tokens per session scan A 768257faf45e
audit is a skill published in the GitHub repository sonomoshq/Canary (2 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 523 once invoked, about $0.0002 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.
Other skills, from other repositories
critique
Find failure modes, edge cases, ambiguities, and exploit paths in plans, code, or designs. Use when reviewing proposals, auditing security, stress-testing logic, or validating assumptions.
explain
Produce clear reasoning with assumptions, causal chains, and evidence. Use when clarifying decisions, teaching concepts, justifying recommendations, or documenting rationale.
audit
Produce a comprehensive audit trail of actions, tools used, changes made, and decision rationale. Use when recording compliance evidence, tracking changes, or documenting decision lineage.
gap-analysis-workflow
Identify capability gaps and propose new skills with prioritization. Use when analyzing missing capabilities, planning skill development, performing ontology expansion, or assessing coverage.
checkpoint
Create a safety checkpoint marker before mutation or execution steps. Use when about to modify files, execute plans, or perform any irreversible action. Essential for the CAVR pattern.
compare
Compare multiple alternatives using explicit criteria, weighted scoring, and tradeoff analysis. Use when choosing between options, evaluating alternatives, or making decisions.