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 Jarroslav/agentic-os/plugin install agentic-sdlcWrote 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/jarroslav/agentic-os/story-intake)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/story-intake"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/story-intake/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/jarroslav/agentic-os/story-intake"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/story-intake.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.00126 | $0.01759 |
| Opus 5 | $0.00063 | $0.00879 |
| Sonnet 5 | $0.00025 | $0.00352 |
| Haiku 4.5 | $0.00013 | $0.00176 |
Grade A, and why
story-intake 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story-intake
Turn exactly one starting input into a single canonical requirements.md, and make sure a
resolvable work-item reference is on file before that document is written.
This is the mouth of the pipeline. Everything downstream (design, planning, complexity, QA, implementation) reads the
requirements.mdyou produce and assumes a work item already exists. Get the normalization right and stay inside the output contract — no phase artifacts leak from here.
When to run
- Automatic:
sdlc-enginecalls this at Phase 1. Human-in-the-loop runs enter throughsdlc-guided; autonomous runs enter throughsdlc-auto. - Direct: a user asks you to normalize a blob of requirements, convert a ticket into requirements, or spec out a greenfield idea.
Do not hand-call this for anything past normalization. Planning, estimation, design, and implementation belong to later phases.
Inputs
| Input | Meaning |
|---|---|
raw_input |
The single starting artifact: text, ticket id/URL, story path, or local work-item path. |
mode_flag |
--greenfield marks the input as a net-new idea with no source ticket. |
run_dir |
The current run directory. All run-scoped writes land under here. |
Detection order (first match wins)
Classify raw_input in this exact order and stop at the first funnel that matches:
--greenfieldflag present → greenfield funnel.- Path matching the local story glob (
docs/stories/*.md) → story-file funnel. - Path matching the local work-item glob (
docs/superpowers/work-items/) → local work-item funnel. - Looks like an external ticket id or URL → ticket-adapter funnel.
- Otherwise → free-form funnel.
Work-item resolution
A work-item reference must resolve before requirements.md is written. Select the source per
funnel:
| Situation | Work-item source |
|---|---|
| Existing local work item | Use its path. |
| Story file | Prefer the story's **Work Item** field; else create/update one under docs/superpowers/work-items/, writing the path back into the story only if editing the story is in run scope. |
| External ticket + adapter receipt | Create/update a local item; store the adapter key/URL in the **External Ticket** field. |
| External ticket, no adapter | Local item with an unresolved external marker (ticket-unresolved:<id>). |
| Free-form / greenfield | Local item keyed by a stable kebab slug derived from the goal. |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 169 lines · 126 tokens per session scan A 553f13ff0708
story-intake is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,759 once invoked, about $0.0006 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.