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 agents/paulbreuler/limps/008-documentationgit clone --depth 1 https://github.com/paulbreuler/limpsWhat 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.00437 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
008-documentation 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 2d 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
Agent 008: Documentation
Objective
Document the context hierarchy and memory system comprehensively.
Tasks
-
Context hierarchy guide (
docs/context-hierarchy.md)- Workspace → Project → Plan → Agent hierarchy
- How inheritance works (CSS-like cascade)
- Override mechanisms
- Root document types (vision, brand, architecture, NFRs)
-
Memory system guide (
docs/memory-system.md)- Agent memory: findings, decisions, blockers
- Plan memory: shared discoveries, lessons
- When to use each type
- Memory CLI reference
-
Workspace setup guide (
docs/workspace-setup.md)limps workspace initwalkthrough- Recommended directory structure
- Template workspace.md
- Best practices for root documents
-
README updates
- Add context hierarchy section
- Link to detailed guides
- Quick examples
Key Topics to Cover
Context Hierarchy
- Why inheritance matters (prevents drift)
- Layer priorities explained
- How to override workspace defaults
- Staleness warnings and what to do
Memory System
- White-box memory philosophy
- Agent memory best practices
- Promoting to plan memory
- Session logging workflow
Root Documents
- vision.md: North star, mission
- brand.md: Terminology, tone
- architecture.md: Technical principles
- nfrs.md: Security, performance
Acceptance Criteria
- All CLI commands documented with examples
- Inheritance rules clearly explained
- Memory workflow guides included
- Root document templates provided
- Follows existing docs style
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.
- 2d ago First seen · 72 lines · 0 tokens per session scan A f289b3a7e4bf
008-documentation is an agent published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 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-31.
Other agents, from other repositories
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
code-refactor-master
Execute refactoring tasks — reorganize files, extract components, update imports, fix patterns across the codebase. Use after a refactor-planner has created a plan.
planner
Autonomous plan quality reviewer using Universal Planning Framework.