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/validating-merges/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/validating-merges)<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/validating-merges"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/validating-merges/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/validating-merges"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/validating-merges.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.00129 | $0.07759 |
| Opus 5.5 | $0.00052 | $0.03104 |
| Sonnet 5.5 | $0.00026 | $0.01552 |
| Haiku 4.5 | $0.00013 | $0.00776 |
Grade D, and why
validating-merges scanned grade D 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 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
`env=os.environ.copy()`). Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
applies a change (its "Run bootstrap" step), and bootstrap calls `sudo`. The no-sudo claim covers only How it starts
The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Gate
Three session types touch a PR and they are not phases of one life:
| type | owns | skill |
|---|---|---|
| build | an item from Ready until its PR exists | build-session |
| closing | the open-PR queue, until merged | closing-session |
| validator | the MERGED PR, until its obligation is discharged | this one |
If the job is "make the change", you are a build session. If it is "get the PRs merged", you are a closing session. If it is "did the merged thing actually work", you are here.
What you own
pr_verifications (issue #1718 half B). The repo-pulse worker opens one row per
merged PR; a documentation-only diff is auto-closed by a deterministic path rule;
everything else stays OPEN until you record evidence. Read the backlog with
python3 scripts/repo_pulse_worker.py --verification-backlog
and record what you concluded with
python3 scripts/pr_verification.py print-schema > ~/.genesis/output/prv-<N>.json
# ... fill it in ...
python3 scripts/pr_verification.py close --pr <N> \
--evidence-file ~/.genesis/output/prv-<N>.json [--note "..."] [--dry-run] \
[--verdict <what you expect>] [--park]
Read back what was decided, and on what evidence, with
python3 scripts/repo_pulse_worker.py --verification-log [--pr <N>]
Two mechanics worth knowing before your first run. --dry-run resolves the
target and renders the record without writing — use it, because a closed row
cannot be amended through this tool. And genesis_db_path() is repo-root
relative, so running the closer from a linked worktree points it at that
worktree's non-existent data/genesis.db: run it from the main checkout or pass
--db-path. The message says so, but the diagnosis is not the one you would
guess.
The backlog is PER INSTALL — each box's worker fills its own ledger against its own deploy state, so two installs hold different open sets and neither one's count says anything about the other.
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 Changed · +196 lines · -1 tokens per session scan A → D 4d9eadda9b05
- 24d ago First seen · 348 lines · 130 tokens per session scan A cbc1bd9dcd1b
validating-merges is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (99 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 7,759 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it D with 2 findings (harvests environment variables, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
verify-before-done
Proves work with tests, diffs, and logs before sign-off.
release-validation
The final "Green Light". Checks all test suites (Unit, Int, E2E) and third-party reports.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
verify
Pre-commit verification entry point. Claude Code 2.1.286+ instructs the model to run a skill named verify right before committing (docs-only and tests-only commits exempt); this thin wrapper delegates that call to the MoAI quality gate instead of hand-rolling substitute checks.