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 agentmods add skills/skyloevil/codex-sdd/tapd-openspec-proposalnpx skills add skyloevil/codex-sdd --skill tapd-openspec-proposalgit clone --depth 1 https://github.com/skyloevil/codex-sddWrote 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/skyloevil/codex-sdd/tapd-openspec-proposal)<a href="https://agentmods.dev/skills/skyloevil/codex-sdd/tapd-openspec-proposal"><img src="https://agentmods.dev/badge/skills/skyloevil/codex-sdd/tapd-openspec-proposal.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00760 |
| Opus 5 | $0.00028 | $0.00380 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
codex-sdd:tapd-openspec-proposal 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 3d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TAPD OpenSpec Proposal
Overview
Use openspec_fetch_tapd_story from the main codex-sdd MCP server to fetch TAPD story content before calling openspec_create_change. In older installations that do not expose this tool, fall back to the project-local tapd-requirement:fetch_story MCP server. Treat TAPD as source material for scope, background, constraints, out-of-scope notes, and acceptance criteria.
Workflow
- Extract TAPD input from the user message:
- URL example:
https://www.tapd.cn/tapd_fe/12345678/story/detail/1000000000000000001 - Parsed workspace id:
12345678 - Parsed story id:
1000000000000000001
- URL example:
- Call MCP tool
openspec_fetch_tapd_storywith either:{ "url": "<tapd story url>" }{ "workspaceId": "<workspace id>", "storyId": "<story id>" }- If
openspec_fetch_tapd_storyis unavailable buttapd-requirement:fetch_storyis available, calltapd-requirement:fetch_storywith the same arguments.
- Read
proposalInputfrom the MCP response. If fields are missing, inspectrawfor team custom fields, comments, or rich description fields. - Build the OpenSpec proposal input:
description: TAPD title plus requirement description.background: TAPD business context, source URL, workspace id, story id, owner/status/priority if present.outOfScope: Explicit TAPD non-goals only. If none are present, leave empty and do not invent exclusions.- Acceptance criteria: preserve TAPD criteria verbatim enough to avoid changing intent, then normalize into checkable bullets.
- Before
openspec_create_change, callopenspec_detect_layoutif available. - Call
openspec_create_changewithpreset: "full". - Record the pre-proposal hook result with
openspec_record_hook_result:hookPoint:pre_proposalhookName:openspec_fetch_tapd_storywhen the main MCP tool was used, ortapd-requirement:fetch_storyfor the fallback tool.status:passedwhen TAPD content was fetched,failedwhen the MCP/API call failed, orskippedonly after the user explicitly chooses to paste requirements manually.
What ships with it
1 file 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.
- 3d ago First seen · 44 lines · 57 tokens per session scan A dc3af92eeb4d
codex-sdd:tapd-openspec-proposal is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 760 once invoked, about $0.0003 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
kirby-project-tour
Maps a Kirby project using Kirby MCP tools/resources, including roots, templates, snippets, controllers, models, blueprints, plugins, runtime status, and key config. Use when a user wants a project overview, file locations, or a quick orientation before making changes.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
discover-product
Run a multi-round discovery (persona / pain / JTBD / scenario / MVP / assumptions) and write DISCOVERY.md.
task-record-contract
Use when creating, updating, or reading the task record for a single implementation task. Covers required task sections, no-placeholder rules, files-first task-file frontmatter, work-unit summary template, implementation artifact linkage, and safe GitHub projection posting practices. Backend projections are documented…
setup-agenticloop
Use when a maintainer or human is setting up Agentic Loop in a target project for the first time, when source document names are non-standard or ambiguous, when .agenticloop/project.md is still unconfirmed, or when a human wants to update its development-stage profile. Discovers bounded candidate project docs once…