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-rulesgit 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-rules)<a href="https://agentmods.dev/commands/kernora-ai/agent-sec/agentsec-rules"><img src="https://agentmods.dev/badge/commands/kernora-ai/agent-sec/agentsec-rules.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.00034 | $0.00119 |
| Opus 5 | $0.00017 | $0.00060 |
| Sonnet 5 | $0.00007 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
agentsec-rules 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 3d 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 get_security_baseline. Then present ALL rules to the user grouped by
category, and for each rule show: the statement, its severity, and its cited source. End with the
count and a link to https://agentsec.kernora.ai/baseline.json for the raw data. This is exactly what
the server serves — nothing hidden.
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.
- 3d ago First seen · 8 lines · 34 tokens per session scan A 476f7b5745f1
agentsec-rules is a command published in the GitHub repository kernora-ai/agent-sec (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 119 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 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-famous
Scan the most popular MCP skills to find issues in well-known packages. This is the highest-value content for Skills Sec.
scan-skill
Scan a specific MCP skill by npm package name or GitHub URL.
monitor-events
Scan X and Hacker News for AI/MCP security incidents, generate SkillsSec response posts.
wf-linkedin
Convert LinkedIn post engagers (likes, comments) into qualified leads and send personalized cold emails.