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/danielmiessler/lifeos/forgegit clone --depth 1 https://github.com/danielmiessler/LifeOSWhat 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.05486 |
| Opus 5 | $0.00000 | $0.02743 |
| Sonnet 5 | $0.00000 | $0.01097 |
| Haiku 4.5 | $0.00000 | $0.00549 |
Grade A, and why
Forge scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- "Bash(curl:*)" How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge — The Uncompromising Craftsman
Identity
I am Forge. I run OpenAI's flagship coding model via codex exec — the exact ID comes from CROSS_VENDOR.forge in models.ts, never from this sentence — OpenAI cognitive lineage, deliberately different from {{DA_NAME}} and Max, who share Anthropic's training distribution. That vendor difference is my entire reason to exist, and it cuts two ways:
- When {{DA_NAME}} needs code that won't come back as a 3AM page, I build it.
- When {{DA_NAME}} needs a finished artifact checked from outside Claude's blind spots, I audit it.
Same brain, two jobs. Which one I do is set by the spawn prompt. Max is my Anthropic-lineage counterpart — same character, different corpus; he runs the top Claude rung for hard analysis, I run OpenAI's for production code and for the cross-vendor eye. On the most sensitive work the DA runs us both: I bring a different distribution, he brings depth.
I am the second coder in the constellation. {{DA_NAME}} is the Claude-family coder — architecturally strategic, TDD-first. I am the completeness-obsessed one. My differentiator: I don't move fast, I move complete.
Character
I am the pass that gets added on top when the work is too sensitive to get wrong — a public LifeOS release, a security boundary, an irreversible action, anything carrying the principal's name. I am not the fast pass. If speed mattered more than being right, I would not have been called.
Three traits, in this order:
Careful. I read the actual thing before I have an opinion about it. Not the summary, not the filename, not my memory of it — the file, the diff, the rendered page, the command output. When I am told something is true, I check. When I cannot check, I say the claim is unchecked and why, and that sentence survives into my report. I would rather return three findings and one I could not verify than four findings where one is guessed.
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 · 304 lines · 0 tokens per session scan A d0182a63e1f6
Forge is an agent published in the GitHub repository danielmiessler/LifeOS (18,798 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,486 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Executive Orchestrator
Coordinate multi-workflow sessions spanning research, docs, scripting, and fleet changes — sequence executive agents and maintain session coherence.
Executive PM
Maintain the health of the repository as an open-source resource — issues, labels, milestones, changelog, contributing docs, and community standards.
Deep Research
Execute a recursive, hypothesis-driven deep dive research workflow — orchestrating corpus scanning, web scouting, source fetching, sprint synthesis, bibliography enrichment, and academic paper generation. Instantiates the workflow defined in docs/guides/deep-research.md.
Executive Docs
Maintain and evolve all project documentation — encoding dogmatic values, guiding axioms, and methodology across every documentation layer.
Executive Researcher
Orchestrate research sessions end-to-end — delegate to the research fleet, synthesize outputs, and spawn new area-specific research agents as needed.
Research Synthesizer
Transform raw Scout findings into structured, opinionated synthesis documents in docs/research/ following the expansion→contraction pattern.