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 haowjy/creative-writing-skills --skill project-setupgit clone --depth 1 https://github.com/haowjy/creative-writing-skillsWrote 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/haowjy/creative-writing-skills/project-setup)<a href="https://agentmods.dev/skills/haowjy/creative-writing-skills/project-setup"><img src="https://agentmods.dev/badge/skills/haowjy/creative-writing-skills/project-setup/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/haowjy/creative-writing-skills/project-setup"><img src="https://agentmods.dev/badge/skills/haowjy/creative-writing-skills/project-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00036 | $0.00767 |
| Opus 5 | $0.00018 | $0.00383 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
project-setup 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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup
Guide the author through setting up their creative writing project. The goal
is a working CLAUDE.md and directory structure that all agents read for
project-specific conventions, plus initial style files if writing samples are
available.
Learn About the Project
Ask about:
- What kind of project: novel, short story collection, serial?
- How far along: starting fresh, or existing chapters and worldbuilding?
- Single POV or multiple? Linear or non-linear timeline? How much worldbuilding?
- Where do they keep their writing? What's the existing layout?
Writing Samples and Style
Ask about writing samples: these are the foundation for style analysis:
- Do they have sample chapters or scenes already written?
- Do they have writing from other projects that captures the voice they want?
- Are there published works they want to draw style inspiration from?
- Voice goals: close third, omniscient, first person? Formal, colloquial?
Collect whatever they have. Save samples to kb/samples/ so they're available
for future style analysis. If they have enough material, offer to analyze
their style using the /creative-writing-craft methodology: read the samples,
identify the voice dimensions, and produce initial style files in kb/styles/.
If they're starting fresh with no samples, capture their voice goals in CLAUDE.md so style files can be created from early drafts.
Propose and Iterate
Based on what you learn, draft a CLAUDE.md section and show it to the
author. Cover:
- Project overview: what the project is, one paragraph
- Author's space: where the author keeps their writing and how it's organized
- KB structure: what subdirectories exist under
kb/and what they're for. Suggest based on project complexity:- Simple (short story, single POV):
characters/,canon/,styles/, rootvocab.md - Medium (novel, few POVs): add
timeline/ - Complex (series, large world): add
world/,issues/, and domain vocab files such asworld/vocab.md
- Simple (short story, single POV):
- Voice and style: what style files exist, what samples they're derived from, voice goals not yet captured
- Conventions: anything project-specific: naming patterns, chapter numbering, POV tagging, spoiler handling
- Shared vocabulary: early canonical terms, aliases, invented words, genre terms with project-specific meanings, and terms the author wants agents to avoid or distinguish
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.
- 10d ago First seen · 82 lines · 36 tokens per session scan A 0539f7bd1e58
project-setup is a skill published in the GitHub repository haowjy/creative-writing-skills (453 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 767 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…