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 agentmods add skills/marc0der/reveng/curate-transcriptnpx skills add marc0der/reveng --skill curate-transcriptgit clone --depth 1 https://github.com/marc0der/revengWrote 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/marc0der/reveng/curate-transcript)<a href="https://agentmods.dev/skills/marc0der/reveng/curate-transcript"><img src="https://agentmods.dev/badge/skills/marc0der/reveng/curate-transcript.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00827 |
| Opus 5 | $0.00019 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
curate-transcript 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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are curating a stakeholder interview transcript. Your job is to remove off-topic passages. All kept text is preserved mechanically — you never write or rewrite any transcript content.
Input
The transcript file path is: $ARGUMENTS
Steps
-
Derive the output path by taking the filename, replacing the
.txtextension with_curated.txt, and placing it underoutput/transcripts/. For example:transcripts/interview-1.txt→output/transcripts/interview-1_curated.txttranscripts/deep-dive.txt→output/transcripts/deep-dive_curated.txt
-
Ensure the output directory exists by running
mkdir -p output/transcripts. -
Copy the original file to the output path using
cp. This creates an exact mechanical copy that preserves all text verbatim. -
Read the output file using the Read tool.
-
Identify passages to remove. Classify content into two categories:
Keep — content directly about the application or its domain:
- Application walkthrough content: screen descriptions, user flows, functionality explanations, how the system behaves
- Domain knowledge: business rules, terminology, processes, regulations that the application implements
- Technical details about the application: architecture, data flows, infrastructure it runs on
- Integrations and dependencies: third-party systems, external services, APIs, data exchanges, upstream/downstream applications the system connects to
Remove — everything else, including but not limited to:
- The incumbent modernisation team's agenda, plans, opinions, or approach discussions
- Stakeholder feature requests or wishlists for new functionality
- Project management discussions: team structure, suppliers, contracts, timelines, staffing, resourcing, delivery plans
- Meeting logistics and scheduling: arranging follow-ups, calendar availability, session housekeeping
- Personal context about individuals: career history, background, role introductions beyond job title
- Technical tangents unrelated to the application itself: DPIA processes, data protection policy, procurement procedures, programme governance
- Social pleasantries, small talk, greetings, sign-offs, thanks, and chitchat
- Meta-discussion about the interview process itself
- Tangential conversation not related to the current application or its domain
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.
- 4d ago First seen · 55 lines · 38 tokens per session scan A c0546647f126
curate-transcript is a skill published in the GitHub repository marc0der/reveng (5 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 827 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…