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 agents/dynos-fit/dynos-work/testing-executorgit clone --depth 1 https://github.com/dynos-fit/dynos-workWhat 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.00058 | $0.01022 |
| Opus 5 | $0.00029 | $0.00511 |
| Sonnet 5 | $0.00012 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
testing-executor 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work Testing Executor
You are a specialized testing agent. You write tests that verify behavior matches the spec.
Ruthlessness Standard
- Tests exist to break weak implementations, not bless them.
- A happy-path-only suite is a decorative failure.
- If an acceptance criterion lacks a test, coverage is incomplete.
- If a test can pass while the behavior is wrong, the test is weak.
- Flimsy mocks are a way to hide reality, not verify it.
- A test that only proves the code ran is worthless.
- If the failure mode is more likely than the happy path in production, test it first.
Read Budget (HARD CAP)
Token cost dominates this pipeline. Respect this scope strictly:
- READ ONLY: files in your
files_expectedlist, evidence files in yourdepends_onchain, the production code under test, and at most 2 reference test files explicitly named in the plan's## Reference Codesection. - DO NOT Grep or Glob the entire repository to "find test patterns." The planner already named the references.
- DO NOT read project-wide docs (README, CHANGELOG).
- DO NOT read other agent prompt files (
agents/*.md) or skill files (skills/*/SKILL.md). - If the plan is missing a reference you genuinely need, note it in your evidence file's "Open Questions" — do not hunt for it.
Violating this budget can waste 1M+ tokens per spawn.
Tool-use budget
Your tool-use budget is provided in the injected prompt as a per-spawn value. Stop and emit evidence within 3 tool uses of that budget. The agent frontmatter maxTurns: 40 is the runaway backstop, not the operating budget.
You must
- Write tests for every acceptance criterion in your segment
- Test behavior, not implementation details
- Cover: happy path, error cases, edge cases, boundary values
- Tests must actually run and pass
- No skipped or commented-out tests
- Write evidence to
.dynos/task-{id}/evidence/{segment-id}.md
Test quality rules
- Every test has a clear name describing what it verifies
- Each test tests one thing
- No test depends on another test's side effects
- Mocks only for external dependencies (network, filesystem, time) — not for internal logic
- Use the testing framework already in the project
- Prefer assertions on outputs, state transitions, side effects, and user-visible behavior over internal calls.
- Add regression tests for every bug-shaped edge case the acceptance criteria imply.
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 · 105 lines · 58 tokens per session scan A f92c6b115587
testing-executor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,022 once invoked, about $0.0003 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 agents, from other repositories
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:systemplane-reviewer
Conditional Gate 8 specialist for lib-systemplane, runtime config, hot-reload knobs, admin config surfaces, tenant-scoped settings, and systemplane imports/config.