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 cass-2003/local-workflow-skill --skill notion-spec-to-implementationgit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/notion-spec-to-implementation)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-spec-to-implementation/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/cass-2003/local-workflow-skill/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-spec-to-implementation.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.00039 | $0.00825 |
| Opus 5 | $0.00019 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
notion-spec-to-implementation 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 6d 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.
This is a copy
100% identical to notion-spec-to-implementation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec to Implementation
Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Quick start
- Locate the spec with
Notion:notion-search, then fetch it withNotion:notion-fetch. - Parse requirements and ambiguities using
reference/spec-parsing.md. - Create a plan page with
Notion:notion-create-pages(pick a template: quick vs. full). - Find the task database, confirm schema, then create tasks with
Notion:notion-create-pages. - Link spec ↔ plan ↔ tasks; keep status current with
Notion:notion-update-page.
Workflow
0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
- Add the Notion MCP:
codex mcp add notion --url https://mcp.notion.com/mcp
- Enable remote MCP client:
- Set
[features].rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- Log in with OAuth:
codex mcp login notion
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
1) Locate and read the spec
- Search first (
Notion:notion-search); if multiple hits, ask the user which to use. - Fetch the page (
Notion:notion-fetch) and scan for requirements, acceptance criteria, constraints, and priorities. Seereference/spec-parsing.mdfor extraction patterns. - Capture gaps/assumptions in a clarifications block before proceeding.
2) Choose plan depth
- Simple change → use
reference/quick-implementation-plan.md. - Multi-phase feature/migration → use
reference/standard-implementation-plan.md. - Create the plan via
Notion:notion-create-pages, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.
3) Create tasks
- Find the task database (
Notion:notion-search→Notion:notion-fetchto confirm the data source and required properties). Patterns inreference/task-creation.md. - Size tasks to 1–2 days. Use
reference/task-creation-template.mdfor content (context, objective, acceptance criteria, dependencies, resources). - Set properties: title/action verb, status, priority, relations to spec + plan, due date/story points/assignee if provided.
- Create pages with
Notion:notion-create-pagesusing the database’sdata_source_id.
What ships with it
18 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.
- agents/openai.yaml 524 B
- assets/notion-small.svg 15 KB
- assets/notion.png 8.3 KB
- evaluations/basic-spec-implementation.json 2.3 KB
- evaluations/README.md 4.3 KB
- evaluations/spec-to-tasks.json 2.5 KB
- examples/api-feature.md 13 KB
- examples/database-migration.md 2.4 KB
- examples/ui-component.md 1.6 KB
- LICENSE.txt 1.0 KB
- reference/milestone-summary-template.md 456 B
- reference/progress-tracking.md 8.8 KB
- reference/progress-update-template.md 420 B
- reference/quick-implementation-plan.md 480 B
- reference/spec-parsing.md 6.8 KB
- reference/standard-implementation-plan.md 3.2 KB
- reference/task-creation-template.md 597 B
- reference/task-creation.md 7.8 KB
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.
- 6d ago First seen · 59 lines · 39 tokens per session scan A 6e22c4c6df44
notion-spec-to-implementation is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 825 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notion-spec-to-implementation, differing in 0 lines, and is treated as a copy.
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.