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 summarybotng/summarybot-ng --skill test-idea-rewritinggit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/test-idea-rewriting)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/test-idea-rewriting"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/test-idea-rewriting/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/summarybotng/summarybot-ng/test-idea-rewriting"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/test-idea-rewriting.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.00051 | $0.01661 |
| Opus 5 | $0.00026 | $0.00830 |
| Sonnet 5 | $0.00010 | $0.00332 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
test-idea-rewriting 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Idea Rewriting
<default_to_action> When transforming test ideas:
- DETECT all "Verify X" patterns via regex
- IDENTIFY appropriate action verb category
- TRANSFORM to "[ACTION] [trigger]; [OBSERVE] [result]" pattern
- PRESERVE all metadata (IDs, priorities, automation types)
- VALIDATE zero "Verify" patterns remain
- OUTPUT in same format as input
Success Criteria: /<td>Verify\s/gi returns 0 matches
</default_to_action>
Quick Reference Card
Transformation Pattern
[ACTION VERB] [specific trigger]; [OUTCOME VERB] [observable result]
Action Verb Quick Reference
| Category | Verbs | Use When |
|---|---|---|
| Interaction | Click, Type, Submit, Navigate, Scroll | UI actions |
| Trigger | Send, Inject, Force, Simulate, Load | API/system actions |
| Measurement | Measure, Time, Count, Profile | Performance checks |
| State | Set, Configure, Enable, Disable, Toggle | Setup actions |
| Observation | Confirm, Assert, Check, Observe | Outcome verification |
Common Transformations
| Before | After |
|---|---|
| Verify login works | Submit valid credentials; confirm session created |
| Verify API returns 200 | Send GET request; assert 200 response within 500ms |
| Verify error displays | Trigger validation error; observe error message |
| Verify data saves | Insert record; query database; confirm fields match |
| Verify performance | Execute 100 requests; measure p99 < 200ms |
Transformation Rules
Pattern Detection
/<td>Verify\s/gi // HTML table cells
/^Verify\s/gim // Line starts
/"Verify\s[^"]+"/gi // Quoted strings
Transformation Categories
API/Network Tests
| Input Pattern | Output Pattern |
|---|---|
| Verify API returns X | Send [METHOD] request; assert [STATUS] response |
| Verify endpoint accepts Y | Post [PAYLOAD] to endpoint; confirm [RESPONSE] |
| Verify webhook fires | Trigger [EVENT]; observe webhook received |
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.
- 5d ago First seen · 230 lines · 51 tokens per session scan A fff4f1056446
test-idea-rewriting is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,661 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-09-03.
Other skills, from other repositories
quality-gate
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
golden-dataset
Golden dataset lifecycle patterns for curation, versioning, quality validation, and CI integration. Use when building evaluation datasets, managing dataset versions, validating quality scores, or integrating golden tests into pipelines.
Boundary Value Generator
Generate boundary value test cases for numeric ranges, string lengths, date ranges, collection sizes, and domain-specific constraints using systematic analysis techniques.
ISTQB Test Design Techniques
Apply classic test design techniques the ISTQB way, equivalence partitioning, boundary value analysis, decision tables, state transition testing, and pairwise combinations, to derive minimal high-coverage test sets from requirements.
plugin-test
A testing guide for Zhin.js plugins using Vitest, a JavaScript and TypeScript testing framework. It focuses on checking command and tool behavior, ordinary business logic, and the plugin package’s required structure.