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 agentmods add skills/truecourse-ai/truecourse/truecourse-hooksnpx skills add truecourse-ai/truecourse --skill truecourse-hooksgit clone --depth 1 https://github.com/truecourse-ai/truecourseWrote 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/truecourse-ai/truecourse/truecourse-hooks)<a href="https://agentmods.dev/skills/truecourse-ai/truecourse/truecourse-hooks"><img src="https://agentmods.dev/badge/skills/truecourse-ai/truecourse/truecourse-hooks.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.00017 | $0.01022 |
| Opus 5 | $0.00009 | $0.00511 |
| Sonnet 5 | $0.00003 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
truecourse-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 6d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TrueCourse Hooks
Install, configure, and manage the pre-commit hook that blocks new violations before they land in git.
Important
- Always invoke via
npx -y— without-y, npx will hang on the "Ok to proceed?" prompt whenever the user hasn't cached the latesttruecourseversion. - The hook makes commits slower. Every commit runs
truecourse analyze --diff. On large repos that can be tens of seconds per commit. Make sure the user knows before you install. - Baseline required. The hook diffs against
.truecourse/LATEST.json. The user needstruecourse analyzeto have run at least once. Onmain, they should also commit the resultingLATEST.jsonso the hook works in fresh clones andgit worktree addcheckouts without a per-checkout cold-start. If no baseline exists yet, suggest/truecourse-analyzefirst. hooks.yamlis the single source of truth. Installation creates<repo>/.truecourse/hooks.yamlwith defaults; edit it to change policy. The file is meant to be committed so the whole team shares one hook config.
Instructions
1. Figure out what the user wants
- "install", "set up", "enable" → Install flow
- "status", "is the hook active", "what does it block" → Status flow
- "uninstall", "remove", "disable" → Uninstall flow
- "change what blocks", "make it stricter/looser", "add/remove severities", "enable LLM" → Configure flow
2. Install flow
- Tell the user the tradeoff upfront: commits will be slower; the hook needs a
.truecourse/LATEST.jsonbaseline (run analyze onmainand commit the file so it propagates to clones and worktrees); policy lives in.truecourse/hooks.yamlwhich they should also commit. - Run:
npx -y truecourse hooks install - Relay the output. Two files get created:
.git/hooks/pre-commit(the script git invokes).truecourse/hooks.yaml(starter policy, blockscriticalandhighby default, LLM off)
- If the user hasn't run a full analysis in this repo, suggest
/truecourse-analyze— without a baseline, the hook has nothing to diff against. After analyze onmain, also remind them to commit.truecourse/LATEST.jsonso fresh worktrees/clones inherit it.
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.
- 6d ago First seen · 87 lines · 17 tokens per session scan A 764c33121279
truecourse-hooks is a skill published in the GitHub repository truecourse-ai/truecourse (527 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,022 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
drift-commit-push
Drift-specific git commit and push workflow. Use when preparing commits, choosing conventional commit messages, checking pre-push gates, or deciding whether a push to main is allowed. Keywords: commit, push, git push, conventional commit, pre-push, changelog, risk audit, hooks.
check
Analyze staged git changes with archguardian before committing.
open-draft-pr
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.
panel-review-loop
Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.
address-pr-comments
Triage and address GitHub PR review feedback for fallow, then implement the agreed fixes. Use when the user wants to inspect PR comments, requested changes, or unresolved review threads and act on them.
browser-smoke-review
Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.