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/build-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/build-session)<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/build-session"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/build-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/build-session"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/build-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.00092 | $0.36534 |
| Opus 5.5 | $0.00037 | $0.14614 |
| Sonnet 5.5 | $0.00018 | $0.07307 |
| Haiku 4.5 | $0.00009 | $0.03653 |
Grade C, and why
build-session scanned grade C with 2 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
an `rm -rf` of the production database's parent directory. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
endpoint** (`curl` the real server) or running inside the real service — not How it starts
The opening of the file, as written. The whole thing — 2,261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build 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.
Mandatory read before your first commit:
.claude/skills/genesis-development/references/commit-path.md. It holds the
review_state sequence, the sigils, the Pre-Commit Gate, the depth gate and
verify-RED. Read it; it is not on-demand reference.
Where your session ENDS — build sessions and closing sessions
A session that writes code and a session that drives a PR to merge are different SESSION TYPES, not two phases of one session's life (user decision, 2026-09-02). Loading this skill makes you a build session.
- A build session owns an item from Ready through opening its PR. It runs
the review the change EARNS —
/deep-reviewfor a substantial one, because that is what clears the commit gate's depth check; code-reviewer inline for a small focused fix (the Adaptive Review Protocol below is authoritative, and dispatching a full adversarial pass on a one-line change is not the bar) — and then it is DONE with that item. Where its effect can be observed here, a wrong run can be undone, and it is not on the never-run list, it is seen working BEFORE the PR opens ("Verify BEFORE the PR" below). It does not wait for Codex, and it carries no review loop — the obligations under "When to DRIVE a Merge" (closing-session) pass to the closing session along with the PR; they do not lapse. - A closing session owns the open-PR queue, whichever session built each
PR. Its unit of work is the queue, not the card. That is the
closing-sessionskill; load it instead when the job is "get the open PRs merged". - A cloud coding agent (Devin) is a third kind of builder. It works from the
public repo in its own VM, with no access to an install: no running Genesis, no
~/.genesis/, none of an install's hooks or local reviewers. Hand it only self-contained, spec-complete work whose tests run in CI, off the enforcement-hook surface, as a public issue. Thedevin-readylabel hands it over and starts a paid session, so a session applies it only after the owner explicitly approves that issue in conversation. Once approved, the session applies the label itself; the owner does not apply it by hand. Its PRs join the same queue (closing-session, "Devin-built PRs").
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.
- yesterday Changed · +24 lines 8eeb5d298a56
- 2d ago Changed · +1 lines ebf9f0feb9ed
- 3d ago First seen · 2,236 lines · 92 tokens per session scan C c46a95c14878
build-session is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (99 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 36,534 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-22.
Other skills, from other repositories
git-workflow
Conventional commits, PR creation, and quality gate verification.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
ase-repo-review
Perform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with --unstaged, of the unstaged and untracked changes, with --branch, of a branch against its base, or, with --commit, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited…