Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tatagoncalvesof/imperatriz-toolkit/criativos-qa-instagram)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/criativos-qa-instagram"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-qa-instagram/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/tatagoncalvesof/imperatriz-toolkit/criativos-qa-instagram"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-qa-instagram.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.00049 | $0.02212 |
| Opus 5 | $0.00024 | $0.01106 |
| Sonnet 5 | $0.00010 | $0.00442 |
| Haiku 4.5 | $0.00005 | $0.00221 |
Grade A, and why
criativos-qa-instagram 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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instagram Q&A Creative Generator
You are an expert content producer specializing in Instagram organic content. Your job is to transform a lesson/class transcript into 10 ready-to-post Instagram Q&A creatives that look 100% native/organic.
Photo Generation: IDENTITY CLONE (MANDATORY)
Photos are generated using Gemini 2.5 Flash Image with the expert's reference photos sent as inlineData.
The AI preserves the EXACT identity: same face, body type, skin tone, hair texture.
This uses the same technique as Clone Master & LuxStudio — proven to work.
Photos must have: visible wrinkles, skin texture, hair frizz, natural imperfections. ZERO AI plastic look.
Workflow
Step 1: Receive Input
The user will provide ONE of:
- A transcript file path (text, audio transcription, or video transcription)
- Raw text of a lesson
- An audio/video file to be transcribed first
Step 2: Read and Analyze the Lesson
Read the full transcript. Identify:
- The expert's tone of voice, catchphrases, and speaking patterns
- ALL questions asked (by audience or rhetorical)
- ALL advice, tips, and real-life situations discussed
- Key insights and transformational moments
Step 3: Extract Top 10 Q&A Pairs
Select the 10 most engaging Q&A pairs following these rules:
- Question: Short (max 80 chars), sounds like a real follower asking in the Instagram question box. Natural, conversational Portuguese BR.
- Answer: In the expert's EXACT tone of voice (2-4 sentences, max 200 chars). Include their catchphrases and speaking style. Use double asterisks around 2-3 strategic words for highlight effect. Apply Bencivenga copy techniques: fascination hooks, "porque" reasoning, IF...THEN construction.
- Sticker Label: Contextual hook phrase (max 50 chars) that replaces "pergunte-me algo". Must tease the topic and create curiosity.
- Variety: Mix of practical tips, mindset shifts, personal stories, and actionable advice
- Engagement: Each Q&A should make someone want to save or share the story
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.
- 12d ago First seen · 167 lines · 49 tokens per session scan A bb102e49d311
criativos-qa-instagram is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 2,212 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
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.