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 ggemba/squad-mcp --skill enable-journalinggit clone --depth 1 https://github.com/ggemba/squad-mcpWrote 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/ggemba/squad-mcp/enable-journaling)<a href="https://agentmods.dev/skills/ggemba/squad-mcp/enable-journaling"><img src="https://agentmods.dev/badge/skills/ggemba/squad-mcp/enable-journaling.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.00000 | $0.01239 |
| Opus 5 | $0.00000 | $0.00620 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
enable-journaling 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 8d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Enable Journaling
Objective
Help the user opt in to auto-journaling capture plumbing (PR1 / Fase 1a).
This installs an opt-in Claude Code PostToolUse hook that records work-trail
metadata — a timestamp, the tool name, and the edited file path — into a
local staging file (.squad/pending-journal.jsonl). It captures NO file
contents.
This skill does two things and nothing else:
- Copies the two bundled hook scripts (
hooks/post-tool-use.mjsandhooks/journal-event.mjs) into the user's.squad/hooks/,chmod 0o700. - Prints the exact
.claude/settings.jsonPostToolUse snippet for the user to paste themselves.
It is capture-only. The squad's behaviour does not change as a result of enabling journaling — the captured breadcrumbs are not yet read by anything.
Inviolable Rules
- Never auto-write
.claude/settings.json. The skill PRINTS the snippet and the user pastes it. Claude Code settings are the user's to edit — the skill never modifies them, not even with confirmation. - Explicit consent before any copy. Before copying files into
.squad/hooks/, confirm with the user in plain language what will be written and where. No silent file creation. - No
git commit, nogit push. Read-only git is fine for context. The user owns the commit. - No AI attribution in anything this skill writes or prints. Consistent with the squad-wide commit-authorship rule.
- State the scope plainly. Every run MUST tell the user, in plain words, that this is capture plumbing only and that squad behaviour will NOT change until a follow-up release (PR2) adds distillation and retrieval.
Inputs
/squad:enable-journaling
No flags. The skill is interactive — it asks for consent before writing.
Phase 1 — Explain and get consent
Tell the user, in plain language:
- What this installs: an opt-in PostToolUse hook that records metadata only
(timestamp, tool name, edited path) to
.squad/pending-journal.jsonl. It never records file contents. - Scope statement (mandatory): "This is capture plumbing only — squad behaviour will NOT change until a follow-up release (PR2) adds distillation and retrieval. Until then the captured breadcrumbs simply accumulate locally."
- What gets written: two scripts copied into
.squad/hooks/. - What does NOT get written:
.claude/settings.json— the skill prints a snippet for the user to paste themselves.
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.
- 8d ago First seen · 132 lines · 0 tokens per session scan A 75456164f856
enable-journaling is a skill published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,239 tokens. 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-31.
Other skills, from other repositories
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
pr-review
PR self-review — review changes, produce checklist, update rules.
check-pr
Read-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…