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 mrieck/garrys-count --skill goodnight-garrygit clone --depth 1 https://github.com/mrieck/garrys-countWrote 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/mrieck/garrys-count/goodnight-garry)<a href="https://agentmods.dev/skills/mrieck/garrys-count/goodnight-garry"><img src="https://agentmods.dev/badge/skills/mrieck/garrys-count/goodnight-garry/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/mrieck/garrys-count/goodnight-garry"><img src="https://agentmods.dev/badge/skills/mrieck/garrys-count/goodnight-garry.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.00018 | $0.00566 |
| Opus 5 | $0.00009 | $0.00283 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
goodnight-garry 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 10d 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.
What it actually says
Goodnight, Garry
Here are the repos worked on today:
!`~/.claude/garryscount/goodnight-report.sh 2>/dev/null || echo '{"error":"No data found. Is Garry'\''s Count installed and have you written any code today?"}'`
Instructions
Commit and push all repos that need it. Work through each path in the repos array. Follow these rules exactly:
For each repo
- Run
git -C {path} status --shortto check its state - If the directory doesn't exist or the git command fails: report "Skipped (not found)"
- If the working tree is dirty (status output is non-empty):
- Run
git -C {path} add -A - Run
git -C {path} diff --cached --statto see what changed - Run
git -C {path} diff --cachedto read the actual diff - Write a concise, accurate commit message based on what changed
- Run
git -C {path} commit -m "{your message}" - If commit fails, report the error and move to the next repo
- Run
- Check for unpushed commits:
git -C {path} rev-list @{u}..HEAD --count 2>/dev/null || echo "no-upstream" - If the result is a number > 0 or "no-upstream":
- Check if a remote exists:
git -C {path} remote - If no remote: report "Committed (no remote)" and move on
- Try:
git -C {path} push - If push fails (no upstream set): try
git -C {path} push --set-upstream origin $(git -C {path} rev-parse --abbrev-ref HEAD) - If push still fails: report the error
- Check if a remote exists:
- If status was clean and no unpushed commits: report "Already up to date"
Final summary
After processing all repos, output a markdown table:
| Repo | Action |
|---|
- Repo: show only the last 2 path components (e.g.
github/myapp) - Action: one of "Committed + pushed", "Pushed", "Already up to date", "Committed (no remote)", "Skipped", or "Error: {message}"
If repos is empty or there's an error in the JSON, say: "No repos tracked today. Write some code first!"
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.
- 10d ago First seen · 49 lines · 18 tokens per session scan A 181677c16c3a
goodnight-garry is a skill published in the GitHub repository mrieck/garrys-count (4 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 566 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.