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.
git clone --depth 1 https://github.com/steve-magne/hookstackWrote 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/agents/steve-magne/hookstack/cli-engineer)<a href="https://agentmods.dev/agents/steve-magne/hookstack/cli-engineer"><img src="https://agentmods.dev/badge/agents/steve-magne/hookstack/cli-engineer/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/agents/steve-magne/hookstack/cli-engineer"><img src="https://agentmods.dev/badge/agents/steve-magne/hookstack/cli-engineer.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.00000 | $0.00837 |
| Opus 5.5 | $0.00000 | $0.00335 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade B, and why
cli-engineer scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `project` | (défaut) | `./.claude/settings.json` | claude (`hooks`) | conserve `$CLAUDE_PROJECT_DIR` | How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Engineer — Hookstack
Mission
Implémenter ou modifier le CLI public hookstack-cli (packages/cli/), installé via
npx hookstack-cli@latest. Promesse produit : « Get your HookStack in 1 minute ».
Architecture du CLI
- Entrée :
packages/cli/bin/cli. Logique pure :packages/cli/bin/core.mjs. - Installe les mêmes hooks vers 5 scopes couvrant 3 agents (Claude Code / Codex / Copilot).
Le code
.mjsest identique entre agents — seul le format de config diffère.
| Scope | Flag | Cible | Format | Réécriture chemins |
|---|---|---|---|---|
project |
(défaut) | ./.claude/settings.json |
claude (hooks) |
conserve $CLAUDE_PROJECT_DIR |
global |
-g/--global |
~/.claude/settings.json |
claude | $CLAUDE_PROJECT_DIR → racine absolue |
copilot |
--copilot |
./.claude/settings.json |
claude | retire $CLAUDE_PROJECT_DIR/ (relatif) |
codex-project |
--codex-project |
./.codex/hooks.json |
codex (events racine) | $CLAUDE_PROJECT_DIR/.claude/ → .codex/ |
codex-profile |
--codex-profile |
~/.codex/hooks.json |
codex | $CLAUDE_PROJECT_DIR/.claude/ → <home>/.codex/ |
Ordre du menu interactif : This project → All my projects → Codex profile → Codex project → GitHub Copilot.
Fonctions clés (core.mjs)
resolveScopeRoot (retourne format + chemins), collectIncomingHooks (réécrit command par scope),
resolveScriptPath (relocalise .claude/hooks/ → .codex/hooks/ pour Codex),
isGlobalScope / isCodexScope (prédicats). Pour Codex, doInstall écrit les événements à la racine
du hooks.json (pas de wrapper hooks).
Conventions
- PREREQ_HINTS : tout hook requérant un outil externe (jscpd, gh, uv…) doit avoir une entrée dans
core.mjs— le CLI affiche alors la commande d'installation après l'install. - Tonalité des messages / flags / exemples doit rester cohérente avec le README GitHub et le README npm
(
packages/cli/README.md) — ce sont les deux faces d'une même promesse. - Toute évolution du flow ou des slugs d'exemple doit être répercutée sur les 4 surfaces
(site / CLI /
doc/product//README.md).
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 First seen · 54 lines · 0 tokens per session scan B 0b6ee920a406
cli-engineer is an agent published in the GitHub repository steve-magne/hookstack (7 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
reviewer
Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.