Borrowing it
Nothing to install: this file belongs to kint4/autoframe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kint4/autoframe/main/.claude/skills/tc-to-spec/SKILL.mdgit clone --depth 1 https://github.com/kint4/autoframeWrote 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/kint4/autoframe/tc-to-spec)<a href="https://agentmods.dev/skills/kint4/autoframe/tc-to-spec"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/tc-to-spec/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/kint4/autoframe/tc-to-spec"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/tc-to-spec.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.00044 | $0.00507 |
| Opus 5 | $0.00022 | $0.00253 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
tc-to-spec 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tc-to-spec — Requirements to Spec
Type: Functional Description: Takes requirements from any source (pasted text, Notion, Jira, Linear, Confluence, or a plain description) and generates a runnable Playwright spec file.
Input Format
Any of:
- Pasted plain-text requirements or acceptance criteria
- A Notion / Jira / Linear / Confluence URL (fetched via the available MCP connector)
- A natural-language feature description
If the input is a URL and no connector is available, say: "I don't have access to that connector. Please paste the requirements directly here and I'll generate from that." For .pdf / .docx / .csv, ask the user to paste the relevant content.
Output Format
A spec file at tests/e2e/[feature-name]/[feature].spec.ts following the spec conventions in CLAUDE.md, with each requirement mapped to one or more tests across Happy Path, Negative Cases, and Edge Cases.
Step-by-Step Instructions
- Read the spec conventions in CLAUDE.md.
- Acquire the requirements:
- Plain text → use directly.
- URL → fetch via the matching connector; fall back to "paste here" if unavailable.
- Description → ask up to 3 clarifying questions before generating.
- Binary file → ask the user to paste the content.
- Extract discrete, testable acceptance criteria. List them back to the user for confirmation if ambiguous.
- Map each criterion to a test and classify it as Happy Path, Negative, or Edge.
- Check for an existing Page Object and fixture for the feature; if missing, recommend
/new-pageand use rawpagewith aTODOcomment in the meantime. - Generate the spec following all spec conventions (describe grouping, AAA comments, plain-language names).
- Save to
tests/e2e/[feature-name]/[feature].spec.ts. - Show a short traceability summary mapping each requirement to its test name.
Rules
- Never block on a missing connector — always fall back to paste.
- Every requirement must map to at least one test.
- Follow the spec conventions exactly.
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 · 46 lines · 44 tokens per session scan A 451b3f70a91a
tc-to-spec is a skill published in the GitHub repository kint4/autoframe (6 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 507 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
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
playwright
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from…
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.