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/pedromosquera/squadai/agents-mdgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/instructions/pedromosquera/squadai/agents-md)<a href="https://agentmods.dev/instructions/pedromosquera/squadai/agents-md"><img src="https://agentmods.dev/badge/instructions/pedromosquera/squadai/agents-md.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 | $0.01222 | $0.01222 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
squadai 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- squadai CLAUDE.md — 92% identical, 86 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Memory Protocol
docs/memory/ is this project's persistent, indexed memory store for
decisions, learnings, and incidents. It is shared by every agent working in
this repository — use it.
Search first. Before any research, planning, or implementation task, run
/memory-search <query> (or squadai memory search <query>) and pass the
findings as context. Never skip memory-search before architecture or API
decisions.
Capture as you go. After a decision, fix, or discovery, run
/memory-add <note> (or squadai memory add "<note>"). Notes land in
docs/memory/_inbox/ as drafts until promoted.
Housekeeping. Run /memory-promote periodically to graduate inbox drafts
into permanent topic folders, and /memory-reindex after manual edits under
docs/memory/ to keep the search index current.
For deeper multi-query research, delegate to the @librarian agent with a
plain-language question; it returns ranked excerpts from the memory index.
*
o o o .---.
/|\____/|\____/|\____|o o| S Q U A D A I
/ \ / \ / \ '---' x OpenCode
Session Efficiency Protocol
Work token-efficiently. These rules apply to every task in this repository.
Search before read. Locate code with grep/glob first; read only the files and line ranges you need. Never read a whole file when a targeted range works.
Never re-read a file you just edited. The edit either succeeded or errored; trust that result instead of re-opening the file to check.
Summarize long output. When a tool returns more than ~30 lines, extract the relevant findings instead of pasting the whole output into the transcript.
Delegate exploration. Send open-ended codebase exploration to sub-agents and request a compact report (files, symbols, one-line conclusions) — keep raw file dumps out of the main context.
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.
- 5d ago First seen · 125 lines · 1,222 tokens per session scan A 9ac75f860c56
squadai AGENTS.md is an instructions file published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 1,222 tokens to every session, about $0.0061 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-31.
Other instructions, from other repositories
mex CLAUDE.md
Claude Code instructions for mex-memory/mex, a project described as: Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
Dragon-Brain CLAUDE.md
Instructions for iikarus/Dragon-Brain, covering dragon brain — claude.md, the harness, audit remediation (april–may 2026, complete 2026-05-09), the lie this audit closed and the contract that matters now.
repo-context-mcp AGENTS.md
Instructions for nduc99911/repo-context-mcp, covering agents.md — repo-context-mcp, project, layout, commands and conventions.
EGC copilot-instructions.md
Copilot instructions for Fmarzochi/EGC, covering copilot instructions for egc, repository conventions, readme and translations, code review priorities and egc project memory.
codevira CLAUDE.md
Instructions for sachinshelke/codevira, covering codevira — persistent project memory, when to call which codevira tool, at the start of every session, before modifying any file and before adopting a pattern, library, or naming convention.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.