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 instructions/cameronapak/freedom-stack-v3/agents-mdgit clone --depth 1 https://github.com/cameronapak/freedom-stack-v3What 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.00302 | $0.00302 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
freedom-stack-v3 AGENTS.md 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 3d 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.
- 3d ago First seen · 33 lines · 302 tokens per session scan A 25f0a178d2c8
freedom-stack-v3 AGENTS.md is an instructions file published in the GitHub repository cameronapak/freedom-stack-v3 (42 stars, last pushed 4mo ago), with no licence file. It adds 302 tokens to every session, about $0.0015 per session on Opus 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-30.
Other instructions, from other repositories
projektor AGENTS.md
Instructions for TAJD/projektor, covering agents.md, what projektor is, coordination model (read this first), planning and design docs live in the wiki, not the repo and architecture: the service-layer contract (most important).
lantern AGENTS.md
Instructions for WildChildForLife/lantern, covering agents.md, critical rules (read first), commit message rules, project overview and recommended coding process.
datapages copilot-instructions.md
Instructions for romshark/datapages: Read and follow AGENTS.md in the repository root.
claude-mesh CLAUDE.md
Instructions for pouriamrt/claude-mesh, covering claude.md, what this is, commands, scope to one package and l3 end-to-end against a real claude binary.
canvas-drop AGENTS.md
Instructions for markpasternak/canvas-drop, covering agents.md — canvas-drop, how we work (the loop), autonomous full-scope rounds (mark's preferred workflow), compounding learnings across every agent and project rules (load-bearing — from buildbrief.md).
ctxlayer CLAUDE.md
Instructions for stevenn/ctxlayer, covering ctxlayer — claude code briefing, what runs where, architecture pointers, how a claude session should work in this repo and conventions.