Borrowing it
Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. 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/WingedGuardian/GENesis-AGI/main/.claude/skills/spec-session/SKILL.mdgit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/spec-session)<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/spec-session"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/spec-session/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/wingedguardian/genesis-agi/spec-session"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/spec-session.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.00088 | $0.01845 |
| Opus 5.5 | $0.00035 | $0.00738 |
| Sonnet 5.5 | $0.00018 | $0.00369 |
| Haiku 4.5 | $0.00009 | $0.00185 |
Grade A, and why
spec-session 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec session
Load genesis-development (the shared core) first if this session has not:
it holds the review-chain, evidence and private-data rules every session uses.
A minimal skill for now; its process is designed later. Also read:
- the core's "Due diligence before building" and "Architecture Review"
(
.claude/skills/genesis-development/SKILL.md); .claude/skills/genesis-development/references/due-diligence.mdand.claude/skills/genesis-development/references/plan-docs.md;.claude/docs/premise-check.md, and theevaluateskill for any external candidate;build-session's "Generalizability Gate" before a spec names where code runs.
Plan documents carry a structured header
A plan doc that outlives one session (~/.claude/plans/<name>.md) opens with
YAML frontmatter naming what it commits to and what it was written against:
---
plan: <slug> # matches the filename
status: active # active | stalled | superseded | done
updated: 2026-09-15 # last revision of the LIVE section
pinned:
main: <12-hex> # origin/main as of the `updated` date above
binds: "<one line — what adopting this plan commits us to>"
prevents: "<one line — what it forecloses, or nothing>"
---
Quote binds and prevents — they are prose, and unquoted, a ": " makes the
whole header unparseable while a " #" silently truncates the value
(binds: PR #2046 ships first loads as "PR").
Optional decisions: / ledger: / issues: lists name the trackers this plan
executes, in FULL ids, so a reader of either end can find the other. An absent
list means "none" — so only omit it once you have looked; write
issues: unchecked if you have not. In the body,
## ═══ SUPERSEDED BELOW ═══ divides live content from archaeology; no divider
means the whole file is live. What the body must STATE is set by "Due diligence
before building" in the core, for every development plan presented for approval.
pinned.main is the field that pays for itself: it makes
git fetch origin main --quiet && git log --oneline <pinned.main>..origin/main
a one-command staleness read, on a document whose line numbers and PR heads
otherwise go quietly false. The fetch is load-bearing — against an unfetched
origin/main the command prints nothing and reads as "no drift". A moved main
means re-verify, never that the plan is wrong.
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.
- 3d ago First seen · 139 lines · 88 tokens per session scan A 2e90b27d6a8c
spec-session is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (99 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,845 once invoked, about $0.0004 per session on Opus 5.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-10-22.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
notion-automation
Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
make-automation
Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.
req-elicitation
Structured requirements elicitation — derive complete, verifiable requirements from stakeholder goals (IEEE 29148, IREB, EARS).