gsd-plan-phase

gsd-plan-phase is a skill for Claude Code from coco-research/coco. It costs 16 tokens per session (575 once invoked), scanned A, original, no licence file.

A planning helper that writes a detailed PLAN.md file for one project phase and includes checks for verifying the work.

In plain words
What is it for?
Use it to prepare an implementation plan before starting a project phase.
Why use it?
It turns a broad phase of work into documented steps with a way to check whether they are complete.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it to prepare an implementation plan before starting a project phase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/coco-research/coco/gsd-plan-phase
Install

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.

Any agent
npx skills add coco-research/coco --skill gsd-plan-phase
Clone the repo
git clone --depth 1 https://github.com/coco-research/coco

Made for: Claude Code.

Wrote 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.

agentmods badge for gsd-plan-phase

README.md
[![agentmods](https://agentmods.dev/badge/skills/coco-research/coco/gsd-plan-phase.svg)](https://agentmods.dev/skills/coco-research/coco/gsd-plan-phase)
Your own site
<a href="https://agentmods.dev/skills/coco-research/coco/gsd-plan-phase"><img src="https://agentmods.dev/badge/skills/coco-research/coco/gsd-plan-phase.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00575
Opus 5 $0.00008 $0.00287
Sonnet 5 $0.00003 $0.00115
Haiku 4.5 $0.00002 $0.00057

Measured 3d ago against content hash 3a951dfde866, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gsd-plan-phase 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.

systems/gsd/skills/gsd-plan-phase/SKILL.md · 54 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 54 lines · 16 tokens per session scan A 3a951dfde866

Subscribe to this mod's changes

gsd-plan-phase is a skill published in the GitHub repository coco-research/coco (219 stars, last pushed today), with no licence file. It adds 16 tokens to every session and 575 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

infrastructure-rules

Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…

docxology/template · 171 tokens

infrastructure-project

Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.

docxology/template · 40 tokens

template-template

Meta-template exemplar — self-referential introspection of the template repo: infrastructure modules, pipeline DAG, security layers, and public exemplar roster.

docxology/template · 32 tokens

template-docgen

Derived documentation generators for the template research framework. Scripts that write to docs/generated/ and update in-place doc blocks.

docxology/template · 28 tokens

polis-protocol

Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…

ymxlx/polis-protocol · 0 tokens

computer-systems-analyst

Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration…

wonsukchoi/domain-experts · 85 tokens