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 skills add Karthick-Ramachandran/persist-os --skill security-reviewgit clone --depth 1 https://github.com/Karthick-Ramachandran/persist-osWrote 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/karthick-ramachandran/persist-os/security-review)<a href="https://agentmods.dev/skills/karthick-ramachandran/persist-os/security-review"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/security-review/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/skills/karthick-ramachandran/persist-os/security-review"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/security-review.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.00048 | $0.00409 |
| Opus 5 | $0.00024 | $0.00204 |
| Sonnet 5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
security-review 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 11d 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
Skill: Security Review
Purpose
Find security risks before a change is accepted.
Inputs
- Change summary or diff.
- Feature docs.
- Architecture and security docs.
- Test results.
Required Reading
docs/20-security/SECURITY_MODEL.mddocs/20-security/THREAT_MODEL.mddocs/10-architecture/FILE_WRITE_POLICY.mddocs/60-engineering/ENGINEERING_STANDARDS.mddocs/ai/MCP_STRATEGY.md
Output Files
- Relevant feature
REVIEW.md - Relevant feature
COMPLETION_REPORT.md - Security docs, if the accepted behavior changes.
Process
- Identify changed trust boundaries.
- Check path validation, overwrite policy, symlink policy, and dry-run behavior.
- Check dependency, package, template, and preset risk.
- Check for network, telemetry, secrets,
.env, cloud, AI API, or runtime MCP behavior. - Check tests for security-sensitive behavior.
- Classify findings as blockers, risks, or documented acceptable tradeoffs.
Stop Conditions
Stop and request human decision if:
- Runtime network, telemetry, cloud, MCP, AI API, auth, secrets, storage, or file write behavior changes without ADR or security review.
- Existing files can be overwritten by default.
- Writes can escape the project root.
- Secrets could be read, logged, or generated into docs.
- Engineering standards are bypassed for secrets, dependencies, migrations, tests, or completion evidence.
Quality Bar
- Findings are specific and actionable.
- Security claims cite docs or test evidence.
- Remaining risks are explicit.
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.
- 11d ago First seen · 62 lines · 48 tokens per session scan A 44e4e9551884
security-review is a skill published in the GitHub repository Karthick-Ramachandran/persist-os (8 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 409 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
architecture-governance
Keep code changes conformant to a repo's real, declared architecture using ArchSteer. Use when starting work in an unfamiliar repo, before finishing/committing an architecturally significant change (new dependency, new data access, new external call, new layer), or when asked about a codebase's architecture, layers…
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
genie-orca-review
Independent, read-only review of a group, a wish, or a PR on Orca — SHIP / FIX-FIRST / BLOCKED with severity-tagged findings. Council and retro are this skill with a different input.