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/anilcancakir/claude-code-plugins/project-docsnpx skills add anilcancakir/claude-code-plugins --skill project-docsgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWhat 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.00041 | $0.01429 |
| Opus 5 | $0.00020 | $0.00714 |
| Sonnet 5 | $0.00008 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
project-docs 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 2d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Documentation Skill
Patterns and templates for creating project briefs and product requirements documents (PRDs).
Purpose
Create non-technical project documentation that answers:
- What is this project?
- Who is it for?
- Why does it exist?
- What problem does it solve?
This is NOT technical documentation. For technical docs, use CLAUDE.md.
Project Brief vs PRD vs CLAUDE.md
| Document | Purpose | Audience |
|---|---|---|
| project.md | Project identity and goals | Stakeholders, team |
| brand.md | Visual and verbal identity | Designers, marketing |
| CLAUDE.md | Technical configuration | Claude Code |
Project.md Structure
Minimal (MVP/Side Projects)
# [Project Name]
> [Tagline - one memorable sentence]
[2-3 sentence description]
## Problem
[What pain point does this solve?]
## Solution
[How does your project solve it?]
## Target User
[Who is this for?]
Standard (Startups/Products)
# [Project Name]
> [Tagline]
[Description]
## Problem
**What**: [The pain point]
**Who**: [Who experiences it]
**Impact**: [Cost of the problem]
## Solution
[Value proposition]
## Target Audience
**Primary User**: [Role and context]
- Technical level: [Level]
- Key goal: [What they want]
## Core Features
| Feature | Benefit |
|---------|---------|
| [Name] | [User value] |
## Success Metrics
| Metric | Target | Timeframe |
|--------|--------|-----------|
| [KPI] | [Goal] | [When] |
Comprehensive (Enterprise/Funded)
# [Project Name]
> [Tagline]
[Description]
## Executive Summary
[One paragraph overview for executives]
## Problem Statement
**Problem**: [Detailed pain point]
**Evidence**: [Data, research, quotes]
**Who**: [Target segment with size]
**Impact**: [Business cost if unsolved]
## Solution
**Value Proposition**:
For [TARGET USER]
who [NEED/PROBLEM],
[PROJECT NAME] is a [CATEGORY]
that [KEY BENEFIT].
Unlike [ALTERNATIVES],
we [UNIQUE DIFFERENTIATOR].
## Target Audience
### Primary Persona
- **Name**: [Persona name]
- **Role**: [Job title/context]
- **Goals**: [What they want to achieve]
- **Pains**: [Current frustrations]
- **Technical**: [Skill level]
### Secondary Persona
[Similar structure]
## Core Features
### MVP Features (Must Have)
| Feature | Benefit | Priority |
|---------|---------|----------|
| [Name] | [Value] | P0 |
### Future Features (Nice to Have)
| Feature | Benefit | Priority |
|---------|---------|----------|
| [Name] | [Value] | P1/P2 |
## Success Metrics
### Leading Indicators
- [Metric]: [Target] by [Date]
### Lagging Indicators
- [Metric]: [Target] by [Date]
## Market Context
[If market research was conducted]
### Competitive Landscape
| Competitor | Strength | Weakness | Our Advantage |
|------------|----------|----------|---------------|
### Market Size
- TAM: [Total Addressable Market]
- SAM: [Serviceable Addressable Market]
- SOM: [Serviceable Obtainable Market]
## Out of Scope
[What we're explicitly NOT building]
## Risks & Mitigation
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | [High/Med/Low] | [How to address] |
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.
- 2d ago First seen · 270 lines · 41 tokens per session scan A 4476714ba6c4
project-docs is a skill published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 1,429 once invoked, about $0.0002 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
system-boot
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
project-brain
Triggers (all require explicit user request — do NOT activate just because a brain/ folder exists): (1) The user wants to set up project-level memory ("set up project brain", "scaffold project context", "init project brain", "建项目脑"). (2) The user is in a directory containing brain/ AND explicitly asks to resume /…
subagent-strategy
Delegates research and parallel work to sub-agents.
evolution-guide
Explains how Evolving Lite works when the user asks about the system, its features, or how to use it. Triggers on questions like "how does this work", "what is evolving lite", "what hooks are running", "explain the system".
spawn-agent
Spawn worker agents (Gemini CLI or Codex CLI) to keep main context clean. Use for implementation, codebase research, context gathering, or any scoped work that would pollute the orchestrator's context.
flutter-bloc-development
Build Flutter features using BLoC state management, clean architecture layers, and the project's design system. Apply when creating screens, widgets, or data integrations.