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/arkya-ai/claude-context-os/process-docgit clone --depth 1 https://github.com/Arkya-AI/claude-context-osWhat 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.00000 | $0.00186 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
process-doc 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 yesterday.
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
Process an input document into a structured source summary.
Steps:
- Read
templates/claude-templates.mdand find the Source Document Summary template (Template 1). Use the Light Source Summary if this is a small project (under 5 sessions), Full Source Summary otherwise. - Read the document at: $ARGUMENTS
- Extract all information into the template format. Pay special attention to:
- EXACT numbers — do not round or paraphrase
- Requirements in IF/THEN/BUT/EXCEPT format
- Decisions with rationale and rejected alternatives
- Open questions marked as OPEN, ASSUMED, or MISSING
- Write the summary to
./docs/summaries/source-[filename].md. - Move the original document to
./docs/archive/. - Tell me: what was extracted, what's unclear, and what needs follow-up.
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.
- yesterday First seen · 14 lines · 0 tokens per session scan A 31a1ac33e757
process-doc is a command published in the GitHub repository Arkya-AI/claude-context-os (295 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 186 tokens. 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 commands, from other repositories
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
deploy
Deploy Solana program (devnet first, then mainnet).
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
whats-next
Show current project status and suggest next steps.
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.