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 skills add makifbaysal/tasktrooper --skill retest-after-revisiongit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/retest-after-revision)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/retest-after-revision"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/retest-after-revision/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/skills/makifbaysal/tasktrooper/retest-after-revision"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/retest-after-revision.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.00481 |
| Opus 5.5 | $0.00015 | $0.00192 |
| Sonnet 5.5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
retest-after-revision 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.
What it actually says
Retest After Revision
A resubmitted task carries history: earlier passed test cases (matched by title) and criterion approvals marked approved (as of SHA, changed since: files). Neither is free evidence for this round — a stale pass is exactly what lets a fixed bug reappear unnoticed, or a different bug ship under an old verdict.
Procedure
list_test_casesand the criteria lines — read every "changed since" note; it names the files touched since the last approval.get_task_pull_requestfor the changed-file list (this is the named re-test-scope exception, not a code-reading shortcut for the verdict).- Re-run first every case that failed last round, using its original reproduction. Bug fixed → prove it by testing the original symptom, not a nearby path.
- Re-run every case linked to a criterion whose changed-files list touches shared surface: styles/tokens/theme, layout/router, API client, auth/session, migrations/schema, env/config, package manifests/lockfile, i18n catalogues. This is what "plausibly affects" means in practice — a concrete file-category list, not a feeling.
- Run the regression smoke set (regression-checklist).
- Re-send every re-run case with its new result and evidence, prefixed by the new short SHA. A case you deliberately did not re-run keeps its old result only if its criterion line already says "nothing changed since", or its own notes record why the diff cannot reach it — say which, don't just skip silently.
- New behaviour the fix introduced gets new cases, same as any other round.
Red Flags
- Approving a criterion whose line says "changed since" without a fresh run this round.
- Re-running only the case that failed last time when the fix touched a shared file (styles, auth, migrations, …) that many other cases depend on.
- Trusting the developer's "fixed it" without re-running the original failing reproduction.
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 · 26 lines · 38 tokens per session scan A 5608ed533188
retest-after-revision is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 481 once invoked, about $0.0002 per session on Opus 5.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-10-05.
Other skills, from other repositories
qa-acceptance
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
jetson-video-pipeline
Use when planning, executing, and independently validating Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or concise acceptance workflows.
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
proof-recon
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
webapp-testing
Verify a local web app in a real browser with page, element, click, form, console and screenshot evidence. Use after a build or UI change; do not implement features or publish deployments with this skill.