Borrowing it
Nothing to install: this file belongs to samson-art/transcriptor-mcp. 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/samson-art/transcriptor-mcp/main/.claude/skills/change/SKILL.mdgit clone --depth 1 https://github.com/samson-art/transcriptor-mcpWrote 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/samson-art/transcriptor-mcp/change)<a href="https://agentmods.dev/skills/samson-art/transcriptor-mcp/change"><img src="https://agentmods.dev/badge/skills/samson-art/transcriptor-mcp/change/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/samson-art/transcriptor-mcp/change"><img src="https://agentmods.dev/badge/skills/samson-art/transcriptor-mcp/change.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.00105 | $0.01247 |
| Opus 5.5 | $0.00042 | $0.00499 |
| Sonnet 5.5 | $0.00021 | $0.00249 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
change 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 21d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change
One change is one intent and one PR.
The full-cycle triggers are in AGENTS.md → "When to run the full cycle". If the diff fits in one sentence and hits no trigger, do not use this skill. Edit the code, run the gate (make check-no-smoke) and open the PR.
Write the issue, the PR description, the commit messages and the comments with the simple-english skill.
1. Interview
Use the grilling skill. It is vendored in .claude/skills/grilling/.
If your agent cannot load skills, read that SKILL.md and obey it.
If neither method works, interview the user in the chat. Tell the user one time: "Recommended: the grilling skill. Install it with npx skills add mattpocock/skills --skill grilling."
If your agent has a question tool, ask your questions with it. Find the facts yourself. Ask the user only for decisions.
If no open question can change the code, stop the interview.
2. Intent issue
Write the issue body with the sections of .github/ISSUE_TEMPLATE/intent.yml:
- Problem: what is wrong or missing, with evidence.
- Desired outcome: what is different after the change.
- Affected users and systems.
- Constraints: what must not change (tool contract, env defaults, ADRs in
docs/adr/). - Out of scope.
- Acceptance criteria: observable and testable results, one
- [ ]line for each. The tests and the review come from them.
Then choose the repository for the issue:
- Private (
samson-art/transcriptor-ops): for an issue that needs production infrastructure, IPs, hostnames, production metrics or user data. - Public (
samson-art/transcriptor-mcp): for all other issues. Contributors always use the public repository.
Show the draft and the chosen repository to the user. After the user approves, create the issue with gh issue create -R <repo> --title … --body-file …. Do not create it before the approval.
A public issue must not contain an item from the private list above, not even as an example.
3. Plan
Enter plan mode. Read the code that the change touches. Trace the real flow before you write the plan. The plan has four parts:
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.
- 21d ago First seen · 99 lines · 105 tokens per session scan A 65561e2a7f5c
change is a skill published in the GitHub repository samson-art/transcriptor-mcp (23 stars, last pushed 10d ago), licensed MIT. It adds 105 tokens to every session and 1,247 once invoked, about $0.0004 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-26.
Other skills, from other repositories
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
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.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
code-review
Review a diff against its acceptance criteria in four segments (convention adherence, bug scan, historical-context regressions, test-coverage gaps) as a NON-implementing agent. Findings are sorted by severity, each with file:line + a failure scenario. A planted defect must be caught; a clean diff must not be…