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-writegit 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-write)<a href="https://agentmods.dev/skills/minara-ai/media-agent/media-write"><img src="https://agentmods.dev/badge/skills/minara-ai/media-agent/media-write.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.1 | $0.00052 | $0.01626 |
| Opus 5 | $0.00026 | $0.00813 |
| Sonnet 5 | $0.00010 | $0.00325 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
media-write 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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/media-write — Guided Writing & Variant Generation
Write content collaboratively, then generate platform-specific variants.
Prerequisites
Before starting, read these shared library files:
- Read
lib/adapter-discovery.mdfor adapter format.md location - Read
lib/manifest-ops.mdfor manifest creation - Read
lib/humanize.mdfor de-AI writing rules (MUST read before any writing)
Step 1: Get the Brief
Check if a brief exists from /media-idea:
ls -t content/posts/*/brief.yaml 2>/dev/null | head -1
If a brief exists, read it and show the user:
- Topic, angle, outline, target platforms
If no brief exists, ask the user via AskUserQuestion:
- "What do you want to write about?"
- "Who is the audience?" (developers, beginners, specific community)
- "Which platforms should we target?" (show configured platforms)
Step 2: Create Post Directory
SLUG=$(echo "<title>" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-//' | sed 's/-$//')
DATE=$(date +%Y-%m-%d)
POST_DIR="content/posts/${DATE}-${SLUG}"
mkdir -p "$POST_DIR/assets" "$POST_DIR/variants"
Step 3: Guided Section-by-Section Writing
Work through the article section by section:
Interaction model
-
Propose an outline based on the brief/topic. Use AskUserQuestion: "Here's my proposed outline for ''. Approve or suggest changes?" Show 4-7 sections with one-line descriptions.
-
For each section:
- Propose the section content in chat (2-4 paragraphs)
- Use AskUserQuestion: "How does this section look?"
- A) Approve — move to next section
- B) Shorter / more concise
- C) More technical / add code examples
- D) Different angle (provide feedback)
- On approval, append the section to
source.mdusing the Write or Edit tool - User can say "go back to section N" to revise earlier sections
-
The file is the source of truth. All approved content lives in
source.md. Chat is the collaboration channel for drafting and feedback.
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 · 195 lines · 52 tokens per session scan A f5a47c6c4dcc
media-write is a skill published in the GitHub repository Minara-AI/media-agent (6 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,626 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-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-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-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.
story
A Chinese-language routing tool for fiction writers that directs requests to tools for outlining, writing, analysis, reviews, covers, importing novels, browser control, and project management.
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.