Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add cynthiajones34/GBrain --skill skillpack-checkgit clone --depth 1 https://github.com/cynthiajones34/GBrainWrote 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/cynthiajones34/gbrain/skillpack-check)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/skillpack-check"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/skillpack-check.svg" alt="Measured on agentmods" 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.00118 | $0.01241 |
| Opus 5 | $0.00059 | $0.00620 |
| Sonnet 5 | $0.00024 | $0.00248 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
skillpack-check 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 7d 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.
This is a copy
100% identical to skillpack-check — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillpack Check
Contract
Running gbrain skillpack-check returns a JSON report with:
healthy(bool): true if no action needed.summary(string): one-line summary safe to quote in a briefing.actions(string[]): every remediation command. If non-empty, run them.doctor: fullgbrain doctor --fast --jsonoutput (filesystem checks).migrations: applied/pending/partial counts fromapply-migrations --list.
Exit code:
0— healthy, nothing to do.1— action needed. Readactions[]and execute.2— could not determine (binary crash or missing subcommand). Investigate.
When to run
- Daily cron (e.g. your OpenClaw's
morning-briefing):gbrain skillpack-check --quiet. Exit code alone tells you if anything is wrong; surface a one-liner in the briefing only when exit != 0. No JSON noise in happy-path briefings. - On demand:
gbrain skillpack-checkfor the full JSON when debugging. - In a CI pipeline: same pattern — exit code gates, JSON is the evidence.
What to do with the output
Happy path (healthy: true)
Surface the summary in the agent's output only if asked. Nothing else.
Action needed (healthy: false)
The actions[] array contains the commands to run, in order. Execute them:
for cmd in $(echo "$REPORT" | jq -r '.actions[]'); do
eval "$cmd"
done
Common actions[] entries and what they mean:
gbrain apply-migrations --yes— A migration is pending or half-finished. Run this (it's idempotent). If it exitsstatus: "partial", the host has non-builtin cron handlers that need plugin registration — followskills/migrations/v0.11.0.md.gbrain embed --stale— Embeddings are stale.gbrain check-backlinks --fix— Dead links or missing back-links.- Free-text action (no
Run:prefix in the source message) — agent judgment needed. Quote it in the report for the user.
Determine failure (exit 2)
Treat as urgent. Probably means the gbrain binary is missing from $PATH or
a required subcommand crashed. Check:
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.
- 7d ago First seen · 133 lines · 118 tokens per session scan A 3f347ec8b498
skillpack-check is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 1,241 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to skillpack-check, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
flask-werkzeug-attack
Exploit Flask/Werkzeug debugger exposure for traceback and SECRET leaks.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
hermes-plugin-development
Use when: creating, debugging, or integrating Hermes Agent plugins, including Python backend plugins (tools, hooks, routers, middleware) and JavaScript Hermes Desktop runtime plugins.
windows-compat
Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…