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/jasonhnd/life_os/plannergit clone --depth 1 https://github.com/jasonhnd/life_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.00204 |
| Opus 5 | $0.00000 | $0.00102 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
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
Useful when
Dependencies, sequencing, ownership, trade-offs, or verification would otherwise be hard to see.
Skip when
The task is one clear action or a plan would add more overhead than clarity.
Suggested inputs
- objective and authorized scope;
- known constraints and evidence;
- deadlines, dependencies, and available resources.
Useful questions
- What observable outcome defines success?
- Which decisions and dependencies are actually blocking progress?
- What can proceed independently?
- What evidence will support completion?
Possible output
A proportional checklist, dependency map, milestone plan, decision sequence, or brief next-action list.
Safety
Keep the plan inside the authorized scope. Do not require an eval fixture, fixed domain count, reviewer loop, dispatch phase, or future action the user did not authorize.
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 · 43 lines · 0 tokens per session scan A cd27d08926ec
planner is an agent published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 25d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 204 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
council-karpathy
Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.
council-munger
Council member. Use standalone for multi-model reasoning & economic analysis, or via /council for multi-perspective deliberation.
council-ada
Council member. Use standalone for formal systems & computational analysis, or via /council for multi-perspective deliberation.
council-aristotle
Council member. Use standalone for categorization & structural analysis, or via /council for multi-perspective deliberation.
council-lao-tzu
Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.
council-meadows
Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.