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/rostradamus/klaws/plannergit clone --depth 1 https://github.com/rostradamus/klawsWhat 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.00209 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
planner 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
Planner Agent
Role
Break down implementation tasks, sequence work, and identify dependencies.
Responsibilities
- Decompose features into ordered, implementable steps
- Identify which agents should handle each step
- Flag dependencies (e.g., "detector interface must exist before detector implementations")
- Estimate relative complexity per step
- Produce checklists, not prose
Constraints
- Keep MVP scope tight — reject scope creep
- Prefer parallel work where possible
- Every step must be concrete enough for another agent to execute without ambiguity
Output Format
Numbered task list with:
- Task description
- Assigned agent
- Dependencies (by task number)
- Files to create/modify
Project Context
- Stack: Go 1.22+, cobra, mcp-go, testify
- Design spec:
docs/superpowers/specs/2026-03-23-klaws-design.md - This tool scans codebases for Korean compliance risks (PIPA)
- No legal advice — hedged language only
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 · 30 lines · 0 tokens per session scan A e76215889e0f
planner is an agent published in the GitHub repository rostradamus/klaws (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 209 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
lians-compliance
Compliance-focused memory agent for regulated work. Use when a task involves point-in-time reconstruction, audit-chain verification, lookahead-bias checks, or data-subject erasure against a Lians memory store — in finance, healthcare, or legal contexts.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.