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 jamesyang124/agent-skills --skill tech-plan-to-wikigit clone --depth 1 https://github.com/jamesyang124/agent-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/jamesyang124/agent-skills/tech-plan-to-wiki)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/tech-plan-to-wiki"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/tech-plan-to-wiki/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/jamesyang124/agent-skills/tech-plan-to-wiki"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/tech-plan-to-wiki.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.00057 | $0.02951 |
| Opus 5 | $0.00028 | $0.01476 |
| Sonnet 5 | $0.00011 | $0.00590 |
| Haiku 4.5 | $0.00006 | $0.00295 |
Grade A, and why
tech-plan-to-wiki 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 9d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Plan to Wiki
Install this skill globally
Install once — available in all projects.
# Claude
mkdir -p ~/.claude/skills/tech-plan-to-wiki
cp <agent-settings-repo>/.agent-settings/skills/workflows/tech-plan-to-wiki/SKILL.md \
~/.claude/skills/tech-plan-to-wiki/SKILL.md
# Add to ~/.claude/CLAUDE.md: - **tech-plan-to-wiki** (`~/.claude/skills/tech-plan-to-wiki/SKILL.md`)
# Copilot
mkdir -p ~/.copilot/skills/tech-plan-to-wiki
cp <agent-settings-repo>/.agent-settings/skills/workflows/tech-plan-to-wiki/SKILL.md \
~/.copilot/skills/tech-plan-to-wiki/SKILL.md
This skill bridges the Plan and Review phases of the spec-kit native SDD workflow. It reads spec-kit's local output files and publishes a structured design review page to Confluence, giving the team a shared surface to read, comment, and give feedback — without ever editing the source files directly.
Key principle: plan.md and requirements.md are the source of truth. The Confluence page is a shared view for team review only. Team feedback never goes directly into Confluence — it flows back to the lead RD who refines the local spec-kit files, then re-publishes with this skill.
Design Review Template (MANDATORY)
All published pages must follow the template at:
references/design-review-template.md (relative to this skill folder: .agent-settings/skills/tech-plan-to-wiki)
Use the template as the structural skeleton. Populate each section from the spec-kit artifacts. Use [TODO] for gaps — never invent content.
Arguments
All optional — anything not passed is asked for.
| Token shape | Interpreted as |
|---|---|
| all digits | Confluence page ID → update that page instead of creating one |
| anything else | SDD feature directory holding spec.md / plan.md / requirements.md |
No page ID → create mode. Save the returned page ID for re-runs, otherwise a duplicate page is created.
Prerequisites
IMPORTANT: This skill requires the Atlassian MCP Server to be installed and configured.
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.
- 9d ago First seen · 273 lines · 57 tokens per session scan A a8a1b36a1ecc
tech-plan-to-wiki is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,951 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
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.
remove
Remove a deployed framework or addon from the current workspace.