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 boshi-xixixi/TraeSkill --skill breakdown-testgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/breakdown-test)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/breakdown-test"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/breakdown-test/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/boshi-xixixi/traeskill/breakdown-test"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/breakdown-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.03197 |
| Opus 5.5 | $0.00012 | $0.01279 |
| Sonnet 5.5 | $0.00006 | $0.00639 |
| Haiku 4.5 | $0.00003 | $0.00320 |
Grade A, and why
breakdown-test 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- breakdown-test — 100% identical, 0 lines differ
- breakdown-test — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Planning & Quality Assurance Prompt
Goal
Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
Quality Standards Framework
ISTQB Framework Application
- Test Process Activities: Planning, monitoring, analysis, design, implementation, execution, completion
- Test Design Techniques: Black-box, white-box, and experience-based testing approaches
- Test Types: Functional, non-functional, structural, and change-related testing
- Risk-Based Testing: Risk assessment and mitigation strategies
ISO 25010 Quality Model
- Quality Characteristics: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
- Quality Validation: Measurement and assessment approaches for each characteristic
- Quality Gates: Entry and exit criteria for quality checkpoints
Input Requirements
Before using this prompt, ensure you have:
Core Feature Documents
- Feature PRD:
/docs/ways-of-work/plan/{epic-name}/{feature-name}.md - Technical Breakdown:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md - Implementation Plan:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md - GitHub Project Plan:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md
Output Format
Create comprehensive test planning documentation:
- Test Strategy:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md - Test Issues Checklist:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md - Quality Assurance Plan:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md
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.
- 1mo ago First seen · 366 lines · 29 tokens per session scan A 83727ec30a98
breakdown-test is a skill published in the GitHub repository boshi-xixixi/TraeSkill (277 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 3,197 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
testing
A guide for writing tests that check observable behaviour rather than the code's internal structure. Tests are repeatable checks that confirm software still gives the expected result after changes.
verify-and-fix
A development practice for checking that code really works before calling it finished. It uses tests, type checks, and real runs of the target scenario where available.
verification-before-completion
A checklist for verifying work before claiming that it is finished, fixed, built, tested, or ready to submit. It requires fresh command output and evidence for each claim.
ml-data-leakage-guard
Detects and prevents data leakage in machine learning and mathematical modeling. Use after ML tasks involving data cleaning, feature engineering, data augmentation, algorithm development, normalization, missing value imputation, dimensionality reduction, feature selection, or time series modeling. Checks if…
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.