Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add archugunov/pm-job-search/plugin install pm-job-searchWrote 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/archugunov/pm-job-search/story-builder)<a href="https://agentmods.dev/skills/archugunov/pm-job-search/story-builder"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/story-builder/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/archugunov/pm-job-search/story-builder"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/story-builder.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.00167 | $0.03923 |
| Opus 5 | $0.00084 | $0.01962 |
| Sonnet 5 | $0.00033 | $0.00785 |
| Haiku 4.5 | $0.00017 | $0.00392 |
Grade A, and why
story-builder 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/story-builder — maintain the universal STAR-story bank
Conversational skill that builds and maintains userdata/stories/*.md — the universal bank that /interview-prep adapts per-interview. One story per file. Filenames are auto-derived from titles; the user never types a filename.
Voice: every prompt (picker, STAR-section asks, angle drafting) follows ${CLAUDE_PLUGIN_ROOT}/TONE.md. Apply the low-effort-first principle — for a NEW story, accept the user's rough first draft, then ask one targeted question at a time only if the draft needs it. Don't force the full STAR conversation when the user clearly has the story in their head already.
Inputs
- All
userdata/stories/*.mdfiles. Read frontmatter (title,story_type,themes,role_lens,last_practised) — body only when an existing story is selected for editing. userdata/profile.md— read## Positioning,## Proof Points,## Tone of Voice,## What NOT to Frame As. Use Tone of Voice to shape draft prose; check drafts against "What NOT to Frame As" before showing. Readtarget_titlesfrom frontmatter for level-weighting in coverage analysis.- Story taxonomy:
userdata/references/story-taxonomy.mdif present, else${CLAUDE_PLUGIN_ROOT}/references/story-taxonomy.md(userdata override per TONE.md convention). Provides the 12 story types + coverage matrix + level-differentiation patterns. - Optional flags:
--new <"title">skips the picker and goes straight to new-story flow with the given title.--edit <slug>loads a story by filename slug.--gap-checkruns coverage analysis only — no edit flow. See Mode 4 below.
If userdata/profile.md is missing, tell the user to run /setup first.
Mode 1: Picker (default)
If no flag, build a picker. List every userdata/stories/*.md as:
- Payments pricing experiment [themes: growth, pricing, experimentation, post-PMF] (last practised 2026-05-11)
- Cross-functional review process [themes: leadership, process] (last practised 2026-04-22)
- Underwriting integration [themes: 0-to-1, data, fintech] (never practised)
- New story (describe one)
- Cancel
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 · 232 lines · 167 tokens per session scan A ee20599c73f8
story-builder is a skill published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 17d ago), licensed MIT. It adds 167 tokens to every session and 3,923 once invoked, about $0.0008 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
chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.
story-init
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.
revision-continuity
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline consistency, line edit, developmental edit, polish a draft, or prepare existing story material for the next revision pass.
story-maintenance
This skill should be used when the user asks to validate, reindex, repair registries, check links, check continuity, count words, summarize a story project, import an existing manuscript, export a manuscript, run the story CLI, or perform deterministic maintenance on a Story Skills markdown project.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.