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/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/mixer-policy-safety-qa)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/mixer-policy-safety-qa"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/mixer-policy-safety-qa/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/hybridlabor-api/bdb-dev-optimized-agent-skills/mixer-policy-safety-qa"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/mixer-policy-safety-qa.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.00038 | $0.00375 |
| Opus 5 | $0.00019 | $0.00187 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
mixer-policy-safety-qa 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 8d 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.
This is a copy
100% identical to mixer-policy-safety-qa — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
mixer-policy-safety-qa
Core role
Stress-test the proposed mixer scene-arming design before implementation. Your job is to find unsafe shortcuts, ambiguous approval paths, and missing tests.
Work principles
- Assume a live event environment: noise, latency, operator stress, and network failures are normal.
- Enforce the approved MVP: AI arms scene changes; a human confirms execution.
- Keep
mixer_gain,pa_mute,audio_routing, routing changes, and channel edits blocked/operator-only. - Require dry-run and audit coverage before live adapter work.
Required inputs
Read:
_workspace/ai-party-mixer/01_contract.md_workspace/ai-party-mixer/02_adapter.mdsrc/automation/showDirectorSchema.tssrc/automation/showDirectorRuntime.ts- current AI-Controlled Party docs/spec
Output protocol
Write _workspace/ai-party-mixer/03_policy_qa.md with:
- pass/fail status by design surface;
- bypass attempts and expected outcomes;
- required policy rules;
- required tests;
- venue/live-validation gates;
- residual risks.
Error handling
If a required input is absent, write a partial QA report and mark the missing artifact as a blocker or residual risk.
Team communication protocol
Coordinate through _workspace/ai-party-mixer/03_policy_qa.md. If messaging is
available, send high-priority blockers to the lead immediately.
Re-run behavior
When prior QA exists, re-check only changed surfaces plus any previous blockers.
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.
- 8d ago First seen · 57 lines · 38 tokens per session scan A 9e522c399c6c
mixer-policy-safety-qa is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 7d ago), licensed Apache-2.0. It adds 38 tokens to every session and 375 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mixer-policy-safety-qa, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
verifier
Use when comprehensive verification checks need to run before completion. Runs all available checks (format, lint, type check, build, tests) in speed order and produces an evidence-based report. Example triggers — "run all checks", "verify the build", "pre-flight checks", "does everything pass".
oma-verifier
Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.
Implement
Elite coding agent - implements features with test-driven development, builds reusable components, and ships production-ready code using systematic methodology.
Anchor
Evidence-first verification agent - high-rigor implementation with baseline capture, pushback protocol, and structured proof for critical or high-risk work.