Borrowing it
Nothing to install: this file belongs to prebid/salesagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prebid/salesagent/main/.claude/commands/obligation-team.mdgit clone --depth 1 https://github.com/prebid/salesagentWrote 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/prebid/salesagent/obligation-team)<a href="https://agentmods.dev/commands/prebid/salesagent/obligation-team"><img src="https://agentmods.dev/badge/commands/prebid/salesagent/obligation-team/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/commands/prebid/salesagent/obligation-team"><img src="https://agentmods.dev/badge/commands/prebid/salesagent/obligation-team.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.00046 | $0.03943 |
| Opus 5.5 | $0.00018 | $0.01577 |
| Sonnet 5.5 | $0.00009 | $0.00789 |
| Haiku 4.5 | $0.00005 | $0.00394 |
Grade A, and why
obligation-team scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
PASS: @patch("...requests.post") — the delivery function calls requests.post. How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team-Based Obligation Test Generation: $ARGUMENTS
Spawn one agent per obligation. Each agent researches production code, writes a test to a temp file, runs it, fixes it until green, and reports back verified working code. Leader consolidates into the final test file and commits.
Architecture
- Agents: Research + write temp test file + run pytest + fix until green (parallel)
- Team lead: Consolidates verified tests into final file, quality gates, commit
Agents are full team members with shell access. They each write to their own
temp file (tests/unit/_tmp_test_{OID_SUFFIX}.py) so there are no conflicts.
The leader appends verified code to the shared test file after all agents report.
Protocol
Step 0: Resolve obligation IDs
Parse $ARGUMENTS to extract obligation IDs.
If prefix mode (args look like UC-004 --count 10 — no trailing sequence number):
python3 -c "
import json
al = json.loads(open('tests/unit/obligation_coverage_allowlist.json').read())
prefix = '$PREFIX'
matches = sorted(oid for oid in al if oid.startswith(prefix))
count = $COUNT # default 10 if --count not specified
selected = matches[:count]
print('Selected obligations:')
for oid in selected:
print(f' {oid}')
print(f'Total matching: {len(matches)}, selected: {len(selected)}')
"
If direct IDs (args are full obligation IDs separated by spaces):
Verify each ID exists in docs/test-obligations/ or the allowlist.
Store the resolved list as OBLIGATION_IDS.
Step 1: Gather shared context
Read these once — they'll be included in every agent's prompt:
-
Test file header (imports + helpers):
# Identify the test file from the use case prefix # UC-004 → tests/unit/test_delivery_behavioral.py head -110 tests/unit/test_delivery_behavioral.py -
Obligation scenarios for all resolved IDs:
for OID in $OBLIGATION_IDS; do grep -A 30 "$OID" docs/test-obligations/*.md done -
Production files to read (list for the agent prompt):
src/core/tools/media_buy_delivery.pysrc/core/schemas/delivery.pysrc/core/webhook_delivery.pysrc/core/webhook_authenticator.py
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 · 461 lines · 46 tokens per session scan A 387afabfac43
obligation-team is a command published in the GitHub repository prebid/salesagent (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 3,943 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.