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 skills/prebid/salesagent/integratenpx skills add prebid/salesagent --skill integrategit clone --depth 1 https://github.com/prebid/salesagentWhat 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.00084 | $0.01510 |
| Opus 5 | $0.00042 | $0.00755 |
| Sonnet 5 | $0.00017 | $0.00302 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
integrate 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Tests from Stubs
Derive integration tests from existing unit test xfails (Bucket A: "requires real DB") and UNSPECIFIED stubs that exercise DB-dependent paths. Each stub's expected behavior is absolute truth — if the integration test fails, fix production code, never adjust the expected behavior.
Args
/integrate <entity-name-1> [entity-name-2] ...
Entity names (space-separated): creative, media-buy, delivery.
Each must already have a unit test suite from /surface.
Hard Gate: Pre-Check
The catalog atom checks if tests/unit/test_{entity}.py exists. If not:
┌──────────────────────────────────────────────────────────┐
│ STOP: No entity test suite for {entity}. │
│ │
│ Run `/surface {entity}` first to create the │
│ test surface map with obligations and stubs. │
│ │
│ Integration tests derive from the surface — no surface, │
│ nothing to derive from. │
└──────────────────────────────────────────────────────────┘
Protocol
Step 1: Cook the molecule
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/integration-from-stub.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Integrate: {all_args}"
Dry run first (recommended):
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/integration-from-stub.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Integrate: {all_args}" \
--dry-run
Step 2: Walk the molecule
bd ready → bd show <atom-id> → read description → execute → bd close <atom-id> → repeat
Each entity goes through 9 atoms:
catalog → review → triage → architect → write-integration → fix-green → reconcile-xfail → verify → commit
Barrier serialization: Entities execute in parallel within each atom phase,
but write-integration waits for ALL entities' commit from the previous
barrier (if any) to complete. This prevents merge conflicts.
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 · 154 lines · 84 tokens per session scan A fed3307f2572
integrate is a skill published in the GitHub repository prebid/salesagent (36 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 1,510 once invoked, about $0.0004 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-01.
Other skills, from other repositories
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
write-sglang-test
Guide for writing SGLang CI/UT tests. Covers CustomTestCase, CI registration, server fixtures, model selection, mock testing, and test placement. Always read test/README.md for the full CI layout, how to run tests, and extra tips. Use when creating new tests, adding CI test cases, writing unit tests, or when the user…
checking-changes
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
evaluate-pr-tests
Evaluates tests added in a PR for coverage, quality, edge cases, and test type appropriateness. Checks if tests cover the fix, finds gaps, and recommends lighter test types when possible. Prefer unit tests over device tests over UI tests. Triggers on: 'evaluate tests in PR', 'review test quality', 'are these tests…