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 SkillMedev/content-marketing-engine --skill testimonial-capture-interviewgit clone --depth 1 https://github.com/SkillMedev/content-marketing-engineWrote 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/skillmedev/content-marketing-engine/testimonial-capture-interview)<a href="https://agentmods.dev/skills/skillmedev/content-marketing-engine/testimonial-capture-interview"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/testimonial-capture-interview/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/skillmedev/content-marketing-engine/testimonial-capture-interview"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/testimonial-capture-interview.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.00159 | $0.02427 |
| Opus 5 | $0.00079 | $0.01213 |
| Sonnet 5 | $0.00032 | $0.00485 |
| Haiku 4.5 | $0.00016 | $0.00243 |
Grade A, and why
testimonial-capture-interview 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.
This is a copy
100% identical to testimonial-capture-interview — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testimonial Capture Interview
A testimonial that says "great product, great team!" persuades no one, and it is not the customer's fault - it is the interviewer's, because vague questions produce vague praise. The costly mistake this skill prevents is burning a willing customer's only interview slot on questions that yield nothing quotable, then either publishing mush or ghost-writing a quote the customer never said. A well-sequenced interview reliably extracts the before/after story with numbers, and the ethics workflow makes every published word both true and approved.
Operating procedure
The sequence matters most inside the interview itself (Step 3): specifics come before feelings because memory works that way - a customer asked "how do you feel about the product" gives adjectives, but a customer walked through their old workflow first gives numbers, and the feelings that follow attach to those numbers.
Step 1: Select and brief the customer
Pick customers with a measurable outcome and at least 90 days of usage - earlier than that, the "after" hasn't stabilized and the numbers won't survive scrutiny. Send a short brief when scheduling: the purpose (a story about their results, in their words), the time ask (30 minutes), the control they keep (nothing publishes without their written approval of the exact words), and a request to have any relevant numbers handy. The approval promise up front measurably improves both acceptance and candor.
Step 2: Prepare the specifics you already know
Before the call, pull what the account already shows - usage data, support history, the original sales notes on why they bought. Interviewing from zero wastes half the slot on facts you had; interviewing from data lets you ask "your team went from 40 to 300 workflows in Q2 - what happened there?", which is where good soundbites come from.
Step 3: Run the question sequence
Record the call (with consent, stated at the start - recording consent is separate from publication consent and both are required). Then run five phases in order:
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 · 133 lines · 159 tokens per session scan A a03118d6f6ac
testimonial-capture-interview is a skill published in the GitHub repository SkillMedev/content-marketing-engine (1 stars, last pushed 2mo ago), licensed MIT. It adds 159 tokens to every session and 2,427 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to testimonial-capture-interview, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
LinkedIn Post Writer
Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win…
Tweet Thread Builder
Turn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use…
Social Caption Writer
Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a…
Social Content Calendar
Builds a 4-week multi-platform posting calendar for a brand or social team, balancing content pillars, per-channel cadence, and real key dates into a week-by-week grid. Use when the user asks to plan, build, or audit a social content calendar or posting schedule across multiple channels (LinkedIn, X, Instagram…
Social Hook Generator
Generates 10 labeled opening lines for a written social post, one per hook archetype, so the writer can test instead of guess. Use when drafting or rewriting the first line of a LinkedIn post, X post or thread, Instagram caption, or newsletter intro. Do NOT use when the hook is the spoken or on-screen opener of a…
Hashtag Strategist
Builds a tiered hashtag and keyword set sized to the account's actual reach - mixing broad, niche, and branded tags per platform limits and screening out banned, spammy, or shadow-flagged tags. Use when someone asks "what hashtags should I use", "build me a hashtag set for this post", "audit my tag block", or is…