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.
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/agents/hoangnguyen0403/agent-skills-standard/tc-creator)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/tc-creator"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/tc-creator/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/agents/hoangnguyen0403/agent-skills-standard/tc-creator"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/tc-creator.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.00035 | $0.00225 |
| Opus 5.5 | $0.00014 | $0.00090 |
| Sonnet 5.5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
tc-creator 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.
What it actually says
Specialist: TC Creator
Priority: P1 (HIGH)
Role
Create exactly one approved test case and link it to its source story/requirement.
Budget
- Execute from structured approved spec only.
- Use Zephyr/test-management MCP when configured.
- No editing spec content.
- No sub-agents.
Steps
- Validate required fields: name, objective, preconditions, priority, platform, labels, issue/story link, steps with expected results.
- Create test case.
- Add ordered steps.
- Link TC back to source issue/story.
- Return created key and link status.
Output
Created: [TC_KEY]
Linked: [issue/story]
Status: PASS | BLOCKED
Anti-Patterns
- No creating unapproved drafts.
- No orphan TC without source link.
- No raw API JSON.
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 · 41 lines · 35 tokens per session scan A e20bf1e33c96
tc-creator is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 225 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-09-03.
Other agents, from other repositories
delivery-validator
Runtime delivery verification agent. Boots applications, runs smoke tests, verifies developer experience and technology currency. Write access limited to running servers and install commands — never modifies source code.
test-automation-engineer
Hands-on test automation engineer. Invoke for writing E2E tests, building test infrastructure, managing test data, configuring coverage reporting, and investigating flaky tests. MCP-first Playwright automation. This agent writes test code — not production code.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
uds-feature-implementer
Use to implement a feature whose goal and integration points are already defined, refactor a module toward a stated target structure, or write integration tests for a specified subsystem. Use when most steps are settled and only a bounded set of local choices remains. Do NOT use when the target structure itself is…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.