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.
npx agentmods add commands/kernora-ai/agent-sec/agentsec-checkgit clone --depth 1 https://github.com/kernora-ai/agent-secWrote 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/kernora-ai/agent-sec/agentsec-check)<a href="https://agentmods.dev/commands/kernora-ai/agent-sec/agentsec-check"><img src="https://agentmods.dev/badge/commands/kernora-ai/agent-sec/agentsec-check.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 | $0.00022 | $0.00108 |
| Opus 5 | $0.00011 | $0.00054 |
| Sonnet 5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
agentsec-check 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 4d 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
Call the agentsec MCP tool check_action with this action: $ARGUMENTS
Then summarize the cited rules it returns (by id + severity) and, if any apply, recommend a safer approach. Note that this is advisory — a matched rule is guidance; an unmatched action is not an assurance of safety.
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.
- 4d ago First seen · 10 lines · 22 tokens per session scan A 1ce8263e1d1f
agentsec-check is a command published in the GitHub repository kernora-ai/agent-sec (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 108 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.
Other commands, from other repositories
notify-authors
Open GitHub issues on flagged repos to notify authors before public disclosure.
scan-daily
Run incremental ecosystem scan: crawl registries → audit new packages → merge results → generate posts.
scan-skill
Scan a specific MCP skill by npm package name or GitHub URL.
wf-ads
Generate 50-100 ad copy variants from pain point research, then create renderable ad images.
wf-research
Research real customer pain points from Reddit, forums, and social media to fuel ad copy and content.
launch-checklist
Run through the complete launch readiness checklist for Panguard AI.