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 commands/thewaywithin/agent-11/foundationsgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/foundations)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/foundations"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/foundations.svg" alt="Measured on agentmods" 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.00020 | $0.07837 |
| Opus 5 | $0.00010 | $0.03918 |
| Sonnet 5 | $0.00004 | $0.01567 |
| Haiku 4.5 | $0.00002 | $0.00784 |
Grade A, and why
foundations 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.
How it starts
The opening of the file, as written. The whole thing — 1,015 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/foundations Command
PURPOSE
Manage the handoff of BOS-AI foundation documents to AGENT-11. This command scans the documents/foundations/ directory, extracts content to structured YAML schemas, and produces a handoff-manifest.yaml for project context.
Key Design Principle: Extract complete, structured data that agents can parse directly - not lossy prose summaries.
SUBCOMMANDS
/foundations init
Initialize the foundations system - scan documents, extract to structured YAML, generate manifest.
/foundations status
Show current state of all foundation documents with present/extracted/modified status.
/foundations refresh
Re-extract documents that have changed (checksum mismatch).
/foundations validate
Validate that required documents are present and extracted data is complete.
EXECUTION PROTOCOL
Step 1: Parse Subcommand
Extract the subcommand from the user's input:
init- Full initialization with extractionstatus- Show status tablerefresh- Update changed documentsvalidate- Check document and extraction completeness
If no subcommand provided, default to status.
SUBCOMMAND: init
Phase 1: Directory Scan
Scan Location: documents/foundations/
Document Category Matching (case-insensitive, order of precedence):
| Category | Priority 1 | Priority 2 | Priority 3 | Priority 4 | Priority 5 |
|---|---|---|---|---|---|
| prd | prd.md | requirements.md | product-requirements.md | -prd-.md | prd-*.md |
| vision | vision-mission.md | vision.md | strategic-plan.md | vision-and-mission.md | |
| roadmap | strategic-roadmap.md | roadmap.md | development-plan.md | ||
| icp | client-success-blueprint.md | icp.md | personas.md | customer-success.md | |
| research | market-and-client-research.md | market-research.md | competitive-analysis.md | research.md | |
| brand | brand-style-guidelines.md | brand.md | style-guide.md | brand-style-guide.md | |
| marketing | marketing-bible.md | marketing.md | positioning.md | positioning-statement.md | |
| pricing | pricing-strategy.md | pricing.md | pricing-tiers.md |
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 · 1,015 lines · 20 tokens per session scan A 70937a90c571
foundations is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d ago), licensed MIT. It adds 20 tokens to every session and 7,837 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
kb-query
You answer questions against id8Labs knowledge bases, citing sources with Obsidian wikilinks.
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.