Borrowing it
Nothing to install: this file belongs to paullukic/coograph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paullukic/coograph/main/.github/skills/coograph-apply/SKILL.mdgit clone --depth 1 https://github.com/paullukic/coographWrote 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/paullukic/coograph/coograph-apply)<a href="https://agentmods.dev/skills/paullukic/coograph/coograph-apply"><img src="https://agentmods.dev/badge/skills/paullukic/coograph/coograph-apply/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/paullukic/coograph/coograph-apply"><img src="https://agentmods.dev/badge/skills/paullukic/coograph/coograph-apply.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.00027 | $0.01036 |
| Opus 5 | $0.00014 | $0.00518 |
| Sonnet 5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
coograph-apply 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement tasks from an OpenSpec change in openspec/changes/.
Step 1: Identify the change
If a name is provided, look for openspec/changes/<name>/ or openspec/changes/<date>-<name>/.
If no name is provided:
- List directories in
openspec/changes/(excludingarchive/) - If only one active change exists, use it and announce: "Using change: "
- If multiple exist, ask the user to select
Step 2: Read context
Read these files from the change directory:
proposal.md— goals, scope, decisionsspecs/<capability>/spec.md— requirements and acceptance criteriatasks.md— task list and completion status
If any file is missing, report which one and ask the user for its location. Do not confabulate contents.
Show current progress: "N/M tasks complete — working on: "
Step 3: Classify change size
- Quick (≤3 tasks, ≤50 lines changed, no new files): skip full self-verification and auto-review — run a lightweight logic check instead.
- Standard (everything else): run all verification and review steps.
Step 4: Implement tasks
CRITICAL: Follow tasks.md literally. Never reinterpret or regenerate tasks. Never invent field names, API types, or schemas that don't exist in the actual source code.
For each pending task:
- Announce which task is being worked on
- Read every source file to be modified — in full — before making any change
- Grep for every field/type name before using it. If a name cannot be found: STOP, report what's missing, ask the user
- Make the code changes
- Every task MUST result in actual file edits — if a task produces zero edits, it is not complete
- Mark complete in tasks.md:
- [ ]→- [x]
Pause if: task is unclear, implementation reveals a design issue, or an error is encountered.
Step 5: Self-verification (standard changes only)
Before invoking the Reviewer:
- Feature inventory: compare modified files against their original (
git show HEAD:<path>). List features: PRESERVED or REMOVED. Restore any removed without explicit spec request. - Spec text match: re-read the spec. Verify every requirement is implemented. Flag mismatches.
- i18n checks (if project uses i18n): verify new/changed keys exist in all language files.
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.
- 9d ago First seen · 124 lines · 27 tokens per session scan A e0b2f7bbdb2d
coograph-apply is a skill published in the GitHub repository paullukic/coograph (17 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,036 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-08-30.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.