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 Minara-AI/media-agent --skill media-ideagit clone --depth 1 https://github.com/Minara-AI/media-agentWrote 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/minara-ai/media-agent/media-idea)<a href="https://agentmods.dev/skills/minara-ai/media-agent/media-idea"><img src="https://agentmods.dev/badge/skills/minara-ai/media-agent/media-idea/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/minara-ai/media-agent/media-idea"><img src="https://agentmods.dev/badge/skills/minara-ai/media-agent/media-idea.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.00050 | $0.01030 |
| Opus 5 | $0.00025 | $0.00515 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
media-idea 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/media-idea — Brainstorming & Ideation
Brainstorm your next piece of content and produce a structured brief.
Step 1: Understand the User's Direction
Use AskUserQuestion to explore:
Question 1: "What topic or area are you thinking about? It can be vague — we'll sharpen it together."
Question 2: "Who's the audience?"
- A) Developers (general)
- B) Beginners learning to code
- C) Senior engineers / architects
- D) Specific community (describe)
Question 3: "What's the goal of this piece?"
- A) Teach something (tutorial, how-to)
- B) Share an opinion or insight
- C) Announce something (project, release)
- D) Tell a story (case study, post-mortem)
Step 2: Research (Optional)
If the user's topic would benefit from current context, offer to search:
"Want me to look up what's being discussed about this topic right now? I can search for recent articles and discussions to help find a unique angle."
If yes, use WebSearch with 2-3 queries:
- " blog post 2026"
- " developer tutorial"
- " common mistakes"
Summarize findings: what angles are already covered, where there's a gap.
Step 3: Generate Ideas
Based on the user's input and research, propose 3-5 content ideas. For each:
- Title (compelling, specific)
- Angle (what makes this different from existing content)
- Format (tutorial, opinion piece, case study, listicle)
- Estimated length (short: 500-1000 words, medium: 1000-2000, long: 2000+)
Use AskUserQuestion: "Which of these speaks to you? Or describe something different."
Step 4: Develop the Chosen Idea
For the selected idea, propose a detailed outline:
- Hook (opening sentence/paragraph that grabs attention)
- Sections (4-7 sections with one-line descriptions)
- Key takeaway (what the reader leaves with)
- Call to action (what the reader should do next)
Use AskUserQuestion: "How does this outline look?"
- A) Looks good, save the brief
- B) Adjust the outline (describe changes)
- C) Start over with a different idea
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 · 136 lines · 50 tokens per session scan A d98a496b32d2
media-idea is a skill published in the GitHub repository Minara-AI/media-agent (6 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 1,030 once invoked, about $0.0003 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
story-import
A tool for turning an existing novel into a structured writing project. It analyzes the book and organizes its characters, settings, plot plans, chapters, and tracking data for later writing.
story-long-analyze
A long-form fiction analysis workflow for breaking down a novel’s opening chapters, characters, pacing, turning points, relationships, and overall structure.
story-deslop
A writing editor for Chinese web novels that detects writing patterns often associated with AI-generated text and makes the prose feel more natural.
story-short-analyze
A Chinese-language guide for analysing short popular web fiction, such as stories published on 番茄, 故事会, or 知乎盐选. It examines the core premise, plot structure, emotional arc, twists, writing techniques, and reader appeal.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.