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/danielvm-git/bigpowers/simulate-agentsnpx skills add danielvm-git/bigpowers --skill simulate-agentsgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/danielvm-git/bigpowers/simulate-agents)<a href="https://agentmods.dev/skills/danielvm-git/bigpowers/simulate-agents"><img src="https://agentmods.dev/badge/skills/danielvm-git/bigpowers/simulate-agents.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00266 |
| Opus 5 | $0.00018 | $0.00133 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
simulate-agents 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 today.
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.
What it actually says
Simulate Agents
HARD GATE — HARD GATE — Simulations are hypothetical. Do NOT use sim results to make production decisions without validation on real agents. Sims help discover gaps, not replace testing.
Two roles, isolated contexts (no shared state with BUILD agent):
- Mock User — follows Verification Script; reports UX gaps in plain language.
- Auditor — checks CONVENTIONS.md, security checklist, test coverage; structured pass/fail.
Process
- Read story Verification Script + changed files diff.
- Spawn Mock User: step through UAT script; log failures.
- Spawn Auditor: run
audit-codechecklist cold. - Write
specs/SIMULATION-<feature>.mdwith both reports. - Failed items →
respond-revieworplan-workgaps — do not skip human review.
Verify
→ verify: test -f skills/simulate-agents/SKILL.md && test -d specs/verifications
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.
- today First seen · 27 lines · 36 tokens per session scan A 29b4c5436194
simulate-agents is a skill published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 266 once invoked, about $0.0002 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-03.
Other skills, from other repositories
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
backend/testing-guide
后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践.
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求.
bmad-qa-generate-e2e-tests
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]".
133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — finding @acceptance scenarios, happy path with RestAssured, Testcontainers for DB/Kafka, WireMock for external REST. Requires .feature file in context. Part of the…
323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot apps — finding @acceptance scenarios, happy path with RestAssured, @SpringBootTest, Testcontainers for DB/Kafka, WireMock for external REST. Requires .feature file in context. Part of the skills-for-java project.