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 skills/chan4lk/specclaw/contextnpx skills add chan4lk/specclaw --skill contextgit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/context)<a href="https://agentmods.dev/skills/chan4lk/specclaw/context"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/context.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.00061 | $0.00800 |
| Opus 5 | $0.00030 | $0.00400 |
| Sonnet 5 | $0.00012 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
context 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specclaw context
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist.
Manage .specclaw/context.md — the project's living architecture document. All lifecycle skills (plan, build, verify) load this file automatically. It is committed to the project repo so it is shared across the team.
Sub-commands
show
Print the current contents of .specclaw/context.md.
If the file does not exist, print: No context.md found. Run '/specclaw:context add' to create one.
add
Add a new rule, pattern, decision, or constraint to the context document.
- If
.specclaw/context.mddoes not exist, seed it from$CLAUDE_PLUGIN_ROOT/templates/context.mdfirst. - Ask the operator: "What would you like to add? Describe the rule, pattern, or decision — and which section it belongs in (Architecture, Style, Patterns, Decisions, Constraints)."
- Read the current
context.md. - Write the new entry into the correct section. Keep the entry concise (1-5 lines). Preserve all other sections unchanged.
- Write the updated file back to
.specclaw/context.md. - Show the updated section to the operator for confirmation.
- Commit:
git add .specclaw/context.md && git commit -m "docs(context): add <brief description of what was added>".
edit
Rewrite a specific section of the context document.
- If
.specclaw/context.mddoes not exist, seed it from$CLAUDE_PLUGIN_ROOT/templates/context.mdfirst. - Ask the operator: "Which section do you want to edit? (Architecture Overview / Coding Style / Key Patterns / Technology Decisions / Constraints / Recent Decisions)" and "What should the new content be?"
- Read the current
context.md. - Replace only the specified section's content. Preserve all other sections and the document structure (headings, Last updated line).
- Update the
_Last updated_line to today's date. - Write the updated file back to
.specclaw/context.md. - Show the diff (old vs new section) to the operator.
- Commit:
git add .specclaw/context.md && git commit -m "docs(context): update <section name> section".
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.
- 5d ago First seen · 60 lines · 61 tokens per session scan A a1e1cf771b1e
context is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 20d ago), licensed MIT. It adds 61 tokens to every session and 800 once invoked, about $0.0003 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
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
memory-management
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management. Use when: need to store successful patterns, searching for similar solutions, semantic lookup of past work, learning from previous…
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.