Borrowing it
Nothing to install: this file belongs to Vvkmnn/claude-praetorian-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vvkmnn/claude-praetorian-mcp/master/.claude/skills/claude-praetorian/SKILL.mdgit clone --depth 1 https://github.com/Vvkmnn/claude-praetorian-mcpWrote 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/vvkmnn/claude-praetorian-mcp/claude-praetorian)<a href="https://agentmods.dev/skills/vvkmnn/claude-praetorian-mcp/claude-praetorian"><img src="https://agentmods.dev/badge/skills/vvkmnn/claude-praetorian-mcp/claude-praetorian/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/vvkmnn/claude-praetorian-mcp/claude-praetorian"><img src="https://agentmods.dev/badge/skills/vvkmnn/claude-praetorian-mcp/claude-praetorian.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.00030 | $0.00577 |
| Opus 5 | $0.00015 | $0.00289 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
claude-praetorian 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 12d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Praetorian
Context preservation across sessions. Restore before work, compact after valuable findings.
Workflow: restore → work → compact
1. Restore Before Work
Check compactions BEFORE planning, research, or subagents:
praetorian_restore(query="topic") # search — summary mode, ~50 tokens/result
praetorian_restore(query="topic", detail="full") # full detail when summary hit looks relevant
praetorian_restore() # recent compactions
praetorian_restore(project="current") # only this project
When to restore:
- Before planning sessions or architectural decisions
- Before web research — you may already know this
- Before launching subagents — prior context exists
- At session start on a familiar project
- After
/clear— reload lost context
2. Compact After Valuable Findings
Update existing compactions — reuse title to merge, don't create duplicates:
praetorian_compact(type="web_research", title="auth JWT research",
key_insights=[...], refs=[...])
When to compact:
- After research with findings NOT already in compactions
- After decisions worth preserving across sessions
- After subagent results with new insights
- Always reuse existing title to merge — check first
When NOT to compact:
- Routine work, trivial discoveries
- Information already saved in an existing compaction
- Every single web search (only genuinely valuable ones)
3. Manage Storage
praetorian_manage(action="status") # per-project counts, disk size
praetorian_manage(action="prune", count=3) # remove 3 oldest
praetorian_manage(action="prune", project="/path") # prune specific project
Per-project limit: 13. Auto-prunes oldest when exceeded (merges are free). Only mention cleanup to user when >50 total or >500KB.
Tools
| Tool | Purpose |
|---|---|
praetorian_restore |
Search/load past context. Summary mode by default (cheap). |
praetorian_compact |
Save insights. Auto-merges same title+type (>70% Jaccard). |
praetorian_manage |
Storage health: status and prune. |
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.
- 12d ago First seen · 75 lines · 30 tokens per session scan A 82a68d821726
claude-praetorian is a skill published in the GitHub repository Vvkmnn/claude-praetorian-mcp (11 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 577 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-30.
Other skills, from other repositories
hmem-write
Hmem write protocol — picks prefix (L/E/D/P/N/R/I/H…), tree location, and tags, and detects duplicates before persisting. Use before any writememory or appendmemory call (skipping it creates duplicates and misplaced entries), or when the user says 'remember this', 'save this', 'log this', or invokes /hmem-write.
hmem-read
Load long-term memory from hmem via readmemory or loadproject. Use when starting fresh with no L1 summaries, after /compact, when the user asks 'what do you remember', 'continue where we left off', 'was war der letzte Stand', or about a project/topic visible in L1 summaries. Covers search, prefix filter, findrelated…
hmem-config
View and change hmem memory settings, hooks, sync, and checkpoints. Use on /hmem-config, or when the user asks why context is huge, how to change auto-save, how often checkpoints fire, or how to set up sync.
hmem-curate
Curate an .hmem file (your own or foreign) — mark obsolete/irrelevant, fix titles, consolidate duplicates, repair broken links. Requires the hmem-curate MCP server (skill prompts the user to enable it on entry). Use whenever the user says 'aufräumen', 'memory aufräumen', 'Speicher aufräumen', 'hmem aufräumen', 'clean…
hmem-session-start
Mandatory entry point for every Cortex session — invoke at conversation start, after /clear, and after any loadproject call. All stable context (H-entries, projects, device, sync) is pre-injected by the hook — no readmemory(mode='essentials') needed. Surfaces pending git work, Next Steps + open T-tasks, and runs the…
hmem-migrate-o
Migrate O-entries to the v5.3+ project-bound 5-level structure (each O00XX bound to its P00XX). Use on 'migrate O-entries', when hmem-update flags a structure migration, or when you notice O-entries still in the old flat L2→L4→L5 format.