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 spytensor/openmozi --skill creative-writinggit clone --depth 1 https://github.com/spytensor/openmoziWrote 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/spytensor/openmozi/creative-writing)<a href="https://agentmods.dev/skills/spytensor/openmozi/creative-writing"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/creative-writing/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/spytensor/openmozi/creative-writing"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/creative-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00332 |
| Opus 5.5 | $0.00020 | $0.00133 |
| Sonnet 5.5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
creative-writing 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 1mo 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.
What it actually says
Creative Writing Workflow
How to Execute
- Brief: Identify the content type, audience, tone, and key message. Infer from context if not stated.
- Research: If the topic requires factual grounding, use web_search for current information.
- Outline: Structure the piece (intro, body, conclusion) or (hook, development, CTA).
- Draft: Write the full content. Match the requested style and voice.
- Refine: Polish for flow, readability, and impact. Remove filler and tighten language.
Rules
- Match the user's requested tone — formal, casual, humorous, persuasive, etc.
- For blog posts and articles, lead with a compelling hook.
- Keep paragraphs short for digital content.
- If writing social media content, respect platform character limits and conventions.
- Creative work should still be factually accurate — verify claims with web_search.
Pitfalls
- Using a generic tone when the user specified a particular style
- Including unverified statistics or quotes
- Writing overly long content when brevity was requested
- Forgetting to adapt format to the target platform
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.
- 1mo ago First seen · 35 lines · 49 tokens per session scan A a16916350085
creative-writing is a skill published in the GitHub repository spytensor/openmozi (445 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 332 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
one-three-one-rule
1-3-1 decision briefs: problem, three options, one pick.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
workspaces
How an Open SWE workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setupscript and updatescript are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.