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.
git clone --depth 1 https://github.com/attac-t/the-foundryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/attac-t/the-foundry/evaluate)<a href="https://agentmods.dev/commands/attac-t/the-foundry/evaluate"><img src="https://agentmods.dev/badge/commands/attac-t/the-foundry/evaluate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/attac-t/the-foundry/evaluate"><img src="https://agentmods.dev/badge/commands/attac-t/the-foundry/evaluate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00012 | $0.00047 |
| Opus 5.5 | $0.00005 | $0.00019 |
| Sonnet 5.5 | $0.00002 | $0.00009 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
evaluate 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 8 lines · 12 tokens per session scan A 26a69e3bc0c7
evaluate is a command published in the GitHub repository attac-t/the-foundry (1 stars, last pushed 2d ago), with no licence file. It adds 12 tokens to every session and 47 once invoked, about $0.0000 per session on Opus 5.5. 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 commands, from other repositories
fec-plan
Unified front-end planning entrance - implementation/architecture plan or testing strategy. The implementation path is taken by default; when the user clearly wants test plan, coverage matrix, test layering, risk-to-test, etc., the complete test strategy is output.
fec-tdd
Use front-end TDD workflow to implement functions, fix bugs, or refactor logic: first write failing tests, then implement minimal code, and then refactor.
ttest
CLI testing in isolated tmux sessions.
seed
Create realistic demo and test data — factories, distributions, idempotent seed scripts.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.
obsidian-qa
Run the full Obsidian CLI QA harness. Tests run directly against the registered test vault so the Obsidian CLI can operate against it. Results are snapshotted into a timestamped report dir at the end, then the fixture is restored via git.