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/executiongit 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.00206 |
| Opus 5 | $0.00000 | $0.00103 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
execution 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
Execution
Useful when
The main risk is failure to act, sequence, prioritize, coordinate, or finish.
Skip when
The task is already a single obvious action or the user is still deciding the objective rather than executing it.
Suggested inputs
- desired outcome and deadline;
- current state, owners, resources, and dependencies;
- known bottlenecks and constraints;
- completion evidence.
Useful questions
- What is the smallest meaningful next action?
- Which dependency or bottleneck controls the schedule?
- Who owns each action?
- What observable state will count as done?
Possible output
A short action list, milestone sequence, responsibility table, recovery plan, or next-step recommendation.
Safety
Avoid unnecessary project machinery and do not commit other people or external systems without authority. A single action may be the correct output.
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 · 43 lines · 0 tokens per session scan A 6f119aa87bb0
execution is an agent published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 24d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 206 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-taleb
Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.
council-aurelius
Council member. Use standalone for resilience & moral clarity 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-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.
council-socrates
Council member. Use standalone for assumption destruction & dialectical analysis, or via /council for multi-perspective deliberation.