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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill gsd-core-hooksgit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/gsd-core-hooks)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/gsd-core-hooks"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/gsd-core-hooks/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/gsd-core-hooks"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/gsd-core-hooks.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.00216 | $0.01101 |
| Opus 5.5 | $0.00086 | $0.00440 |
| Sonnet 5.5 | $0.00043 | $0.00220 |
| Haiku 4.5 | $0.00022 | $0.00110 |
Grade A, and why
gsd-core-hooks 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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gsd-core-hooks
A rule an agent can read once and forget is not enforced — it's remembered, which is a different thing.
What this is
The .claude/hooks/ directory from one real project (gsd-core), lifted wholesale. Every file here
exists because a specific incident happened first and the hook was written afterward to close the
gap — the header comment on each script names the incident, the date, and the exact failure mode.
This is not a designed-in-advance framework; it is a project's actual scar tissue, in installable
form.
It backs the rules stated in ../commands/ (bug-fixer.md, feature-builder.md,
triage-review.md, test.md) — those files say things like "gsd-test MUST exit 0 before any git
push" and "NEVER run node --test locally"; the hooks in this folder are what make those true
regardless of whether the agent remembers reading them.
The three failure classes it guards against
- Self-attestation. "I ran the tests" / "the review passed" is cheap to claim and expensive to
check by hand.
pre-pr-gate.sh+record-gsd-verdict.shbind a push/PR action to a machine-read verdict line for the exact commit sha being shipped — not "tests passed at some point," but "tests passed for this sha, recorded by the one sanctioned writer, checked at the moment of push." - Prose that goes stale mid-session. A directive is read once, at the start, then hours of
tool calls go by with nothing re-presenting it.
gsd-phase-gate.cjsis the original, project-specific incident behind this project's separately-shipped../artifact-gates/engine — see the note in this folder'sREADME.mdbefore installing both. - Harness ceiling false-negatives. A backgrounded or foregrounded long-running dispatch dies at
the tool harness's own timeout (commonly 600000ms) with no distinguishing signal from a real
failure — and a
pgrep -f "<cmd>"waiter can match its own argv and spin forever even after the watched job finished.gsd-async-poll-guard.sh,gsd-foreground-poll-guard.sh,gsd-pgrep-waiter-guard.sh,gsd-bench-pin-guard.sh, andgsd-test-single-flight-guard.sheach close one verified instance of this.
What ships with it
23 files 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.
- hooks/block-local-node-test.sh 5.9 KB runs code
- hooks/emitted-cjs-read-guard.cjs 7.2 KB runs code
- hooks/gsd-async-poll-guard.sh 7.3 KB runs code
- hooks/gsd-bench-pin-guard.sh 6.7 KB runs code
- hooks/gsd-core-scope.test.sh 1.5 KB runs code
- hooks/gsd-foreground-poll-guard.sh 7.7 KB runs code
- hooks/gsd-merge-authority-guard.cjs 13 KB runs code
- hooks/gsd-merge-authority-guard.test.sh 3.9 KB runs code
- hooks/gsd-pgrep-waiter-guard.sh 6.8 KB runs code
- hooks/gsd-phase-gate-laws.test.sh 3.4 KB runs code
- hooks/gsd-phase-gate.cjs 46 KB runs code
- hooks/gsd-test-clean-tree-guard.sh 11 KB runs code
- hooks/gsd-test-single-flight-guard.sh 14 KB runs code
- hooks/gsd-test-single-flight-guard.test.sh 3.1 KB runs code
- hooks/gsd-test-viability-guard.sh 9.0 KB runs code
- hooks/gsd-verify-and-record.cjs 15 KB runs code
- hooks/lib/prune-gsd-passes.cjs 5.5 KB runs code
- hooks/pre-pr-gate.sh 22 KB runs code
- hooks/record-gsd-verdict.sh 5.2 KB runs code
- hooks/require-memtrace-evidence.sh 7.3 KB runs code
- hooks/require-memtrace-evidence.test.sh 2.3 KB runs code
- hooks/worktree-fresh-base-guard.sh 12 KB runs code
- README.md 9.7 KB
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.
- 1mo ago Changed · +1 lines · +3 tokens per session f0ef27776087
- 1mo ago First seen · 61 lines · 213 tokens per session scan A 215ce60f19ff
gsd-core-hooks is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 216 tokens to every session and 1,101 once invoked, about $0.0009 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-09-04.
Other skills, from other repositories
ci-cd
Use when building or fixing a delivery pipeline. Covers pipeline structure, caching, test parallelization, deployment strategies, secrets, and making the pipeline fast enough that people do not route around it. Trigger on "our ci takes 40 minutes", "flaky pipeline keeps failing", "set up github actions to deploy". Do…
offensive-fuzzing
Practical offensive fuzzing methodology covering target identification, fuzzer selection (AFL++, libFuzzer, Honggfuzz, Boofuzz, syzkaller), harness writing, corpus curation, mutation strategies, coverage measurement, and crash triage. Use when setting up or running fuzz campaigns against any target: file parsers…
offensive-business-logic
Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows…
offensive-race-condition
Race condition (TOCTOU) testing checklist: identifying timing windows, Burp Suite Turbo Intruder, Last-Byte sync technique, rate limit bypass, double-spend attacks, and concurrent request exploitation. Use for web app race condition testing or bug bounty time-of-check-to-time-of-use bugs.
user-story-writer
Escribir historias de usuario bien estructuradas con criterios de aceptación y casos extremos. Úsalo cuando te pidan escribir historias de usuario, crear tickets a partir de un resumen de características, convertir un PRD en historias o redactar criterios de aceptación. Produce historias listas para estimar en formato…
schedule-recipe
Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the…