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-archive/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-archive)<a href="https://agentmods.dev/skills/paullukic/coograph/coograph-archive"><img src="https://agentmods.dev/badge/skills/paullukic/coograph/coograph-archive/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-archive"><img src="https://agentmods.dev/badge/skills/paullukic/coograph/coograph-archive.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.00605 |
| Opus 5 | $0.00014 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
coograph-archive 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 10d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive a completed OpenSpec change by moving it from openspec/changes/ to openspec/changes/archive/.
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/) - Ask the user to select — do NOT auto-select
Step 2: Check task completion
Read tasks.md and count:
- [x]items (complete)- [ ]items (incomplete)
If incomplete tasks exist, warn the user:
"X tasks are still incomplete. Archive anyway?"
Wait for confirmation before proceeding. Do not skip this check.
Step 3: Check for delta specs
Look for openspec/changes/<name>/specs/ — if it contains spec files, compare each against its counterpart in openspec/specs/<capability>/spec.md.
If delta specs exist:
- Show what would change (additions, modifications, removals)
- Ask: "Sync these specs to the main spec files before archiving?"
- If yes: merge each delta spec into its corresponding main spec file. Show what was merged.
- If no: proceed without syncing (delta specs will be archived with the change)
If no delta specs exist: skip this step.
Step 4: Archive
Create the archive directory if it doesn't exist:
mkdir -p openspec/changes/archive
Generate the target name: YYYY-MM-DD-<slug> using today's date.
Check if the target already exists — if so, fail with a clear error and ask the user how to proceed.
Move the change directory:
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<slug>
Step 5: Report
## Archive Complete
**Change:** <name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<slug>/
**Specs:** [Synced to main specs / No delta specs / Sync skipped]
**Tasks:** [All complete / X incomplete — user confirmed]
Guardrails
- Never auto-select a change — always ask the user
- Always check task completion and warn if incomplete — never silently skip
- Always run the delta spec assessment if specs exist
- If the archive target already exists, fail clearly — do not overwrite
- Show a summary of what happened
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.
- 10d ago First seen · 80 lines · 27 tokens per session scan A 9080257fcc18
coograph-archive 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 605 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
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
release-and-changelog
Use when cutting a release, bumping a version, or writing release notes. Activate for keywords like "release", "version bump", "changelog", "release notes", "tag", "publish", "ship a release", "v1.x", "v2.x". Enforces version hygiene: SemVer respect, changelog discipline, atomic commits, tagged release. Always reflect…
compass-release
Release Compass from the latest origin/main. Use this skill whenever a user asks to sync Compass, bump a Compass version, create or merge a release PR, build or publish macOS/Linux/Windows artifacts, write release notes, verify release downloads, or build the matching VS Code VSIX. Follow the complete gated workflow…
ship
Review changes, commit with detailed message, push, and optionally create pull request.
release-checklist
Create go/no-go release checklists with pre-deploy verification, staged rollout steps, monitoring checkpoints, rollback triggers, and stakeholder communication plans.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.