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/dynos-fit/dynos-work/testing-executornpx skills add dynos-fit/dynos-work --skill 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.00031 | $0.00165 |
| Opus 5 | $0.00015 | $0.00082 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
execution/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 2d 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.
What it actually says
dynos-work: execution/testing-executor
Spawn the testing-executor agent with the user's prompt as the instruction.
Ruthlessness Standard
- Do not allow decorative tests that only confirm the happy path.
- The executor must target the actual regression mechanism, boundary condition, and failure mode.
- A test that would pass before the bug fix is wasted output.
What to pass
Pass the user's full prompt verbatim. Do not summarize or sanitize it. Prepend a short hard wrapper that tells the agent to write tests that fail for the real bug, cover the edge behavior, and prove the regression is closed.
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.
- 2d ago First seen · 20 lines · 31 tokens per session scan A 815b480711f9
execution/testing-executor is a skill published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 165 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-08-31.
Other skills, from other repositories
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
ccc-qa
QA workflow. Runs unit + integration + E2E tests, coverage delta, edge case enumeration, flaky test quarantine. Delegates to qa-engineer agent.
testing
· Write/debug tests: unit, integration, E2E, TDD, mocks, fixtures, a11y, perf. Triggers: 'test', 'spec', 'TDD', 'playwright', 'vitest', 'jest', 'pytest', 'coverage', 'flaky'. Not for security tests (use security-audit).
harden
Evidence-driven codebase hardening. Audits security (OWASP Top 10:2025), supply chain (inventory vs SBOM vs SLSA v1.2), reliability (OTel + operational limits), tests (sandboxed tiers), and accessibility (WCAG 2.2 AA). Every finding is quoted, matrix-scored, and cited. Does not fix. Reports with file:line and a…