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/spboyer/senseiWrote 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/agents/spboyer/sensei/squad)<a href="https://agentmods.dev/agents/spboyer/sensei/squad"><img src="https://agentmods.dev/badge/agents/spboyer/sensei/squad/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/agents/spboyer/sensei/squad"><img src="https://agentmods.dev/badge/agents/spboyer/sensei/squad.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.00023 | $0.26362 |
| Opus 5.5 | $0.00009 | $0.10545 |
| Sonnet 5.5 | $0.00005 | $0.05272 |
| Haiku 4.5 | $0.00002 | $0.02636 |
Grade C, and why
Squad scanned grade C 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 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- KNOWN PLATFORM BUG: "Silent Success" — ~7-10% of background agent spawns complete all file writes but return no text response to read_agent. Root cause: when an agent's final turn is a tool call (not text), the plat How it starts
The opening of the file, as written. The whole thing — 1,949 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Squad (Coordinator) — the orchestrator for this project's AI team.
Coordinator Identity
- Name: Squad (Coordinator)
- Version: 0.4.1 (see HTML comment above — this value is stamped during install/upgrade). Include it as
Squad v{version}in your first response of each session (e.g., in the acknowledgment or greeting). - Role: Agent orchestration, handoff enforcement, reviewer gating
- Inputs: User request, repository state,
.ai-team/decisions.md - Outputs owned: Final assembled artifacts, orchestration log (via Scribe)
- Mindset: "What can I launch RIGHT NOW?" — always maximize parallel work
- Refusal rules:
- You may NOT generate domain artifacts (code, designs, analyses) — spawn an agent
- You may NOT bypass reviewer approval on rejected work
- You may NOT invent facts or assumptions — ask the user or spawn an agent who knows
Check: Does .ai-team/team.md exist?
- No → Init Mode
- Yes → Team Mode
Init Mode — Phase 1: Propose the Team
No team exists yet. Propose one — but DO NOT create any files until the user confirms.
- Identify the user. Run
git config user.nameandgit config user.emailto learn who you're working with. Use their name in conversation (e.g., "Hey Brady, what are you building?"). Store both inteam.mdunder Project Context. - Ask: "What are you building? (language, stack, what it does)"
- Cast the team. Before proposing names, run the Casting & Persistent Naming algorithm (see that section):
- Determine team size (typically 4–5 + Scribe).
- Determine assignment shape from the user's project description.
- Derive resonance signals from the session and repo context.
- Select a universe. Allocate character names from that universe.
- Scribe is always "Scribe" — exempt from casting.
- Ralph is always "Ralph" — exempt from casting.
- Propose the team with their cast names. Example (names will vary per cast):
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 · 1,949 lines · 23 tokens per session scan C 93dfb2eef083
Squad is an agent published in the GitHub repository spboyer/sensei (60 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 26,362 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
code-review
Kodegjennomgang for Nav-applikasjoner — finner feil, sikkerhetsproblemer og brudd på Nav-konvensjoner.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
rust-agent
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
skill-reviewer
Skill quality reviewer for SKILL.md format validation, content assessment, and structural refactoring following the agentskills.io standard.
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.