Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mathiasbourgoin/rosternpx agentmods add skills/mathiasbourgoin/roster/roster-configWrote 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/skills/mathiasbourgoin/roster/roster-config)<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/roster-config"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/roster-config/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/skills/mathiasbourgoin/roster/roster-config"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/roster-config.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.00015 | $0.01276 |
| Opus 5 | $0.00008 | $0.00638 |
| Sonnet 5 | $0.00003 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
roster-config 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roster Config
You help users discover and configure the tunables exposed by their installed roster agents. You read installed agent files, surface available settings grouped by impact tier, and rewrite frontmatter for any changes the user approves.
Scope: operates on agents installed in the current project (.claude/commands/ or .harness/agents/ or agents/). Falls back to the roster source tree if no installed harness is found.
Steps
Step 1 — Locate installed agents
# Priority order: installed harness → claude commands → roster source
[ -d .harness/agents ] && echo ".harness/agents" || \
([ -d .claude/commands ] && echo ".claude/commands") || \
([ -d agents ] && echo "agents (roster source)")
If no agent directory is found, report:
⚠️ No installed harness found. Run
/roster-initfirst, or run this from a project with an installed roster harness.
Step 2 — Collect all tunables
Walk all .md files in the found directory. For each file with a tunables: frontmatter block, extract:
- Agent name (from
name:or filename) - Each key-value pair under
tunables: - Inline comment if present (the
# ...after the value)
Build an inventory: { agent, key, value, description, has_ext_dep }.
Mark has_ext_dep: true for any tunable whose inline comment or description mentions pip install, npm install, brew install, or a package name.
Step 3 — Display grouped inventory
Present tunables grouped by tier:
📦 Roster Config — Installed Tunables
🔴 Tier 1 — Optional capabilities with external deps
kb-agent › search_index false # set true to enable LanceDB semantic index
dep: pip install lancedb OR npm install @lancedb/lancedb
🟡 Tier 2 — Project-specific paths (must be customized)
migration-guard › schema_module "" # path to module containing current_version and all_ddl
migration-guard › migration_test_file "" # path to the migration-path test file
pr-workflow › pre_push_validator "" # e.g. "gitwright validate" — leave blank to skip
pr-workflow › pre_pr_checks "" # project-specific pre-PR command
🟢 Tier 3 — Feature toggles (safe defaults, may want to flip)
kb-agent › embedding_mode remote # remote | disabled; disabled keeps deterministic gates offline
implementer › use_worktree true
reviewer › require_security_pass true
tech-lead › require_review true
tech-lead › require_qa true
architect › enforce_architecture_doc true
...
⚙️ Tier 4 — Numeric thresholds
architect › max_file_lines 500
architect › max_function_lines 50
tech-lead › max_parallel_implementers 5
...
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +2 lines · -12 tokens per session ed04fa06ea66
- 10d ago First seen · 125 lines · 27 tokens per session scan A faf4c24369dc
roster-config is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 1,276 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…