Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nick-pape/grackle/main/.claude/skills/readme-refresh/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/readme-refresh)<a href="https://agentmods.dev/skills/nick-pape/grackle/readme-refresh"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/readme-refresh/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/nick-pape/grackle/readme-refresh"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/readme-refresh.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.00031 | $0.01947 |
| Opus 5.5 | $0.00012 | $0.00779 |
| Sonnet 5.5 | $0.00006 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
readme-refresh 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Refresh — Automated Screenshot & Copy Update
This skill detects staleness in the project README and its screenshots, captures fresh screenshots from the running web UI, and drafts updated README content. It leaves all changes unstaged for the user to review.
Step 1: Research Phase
Launch up to 3 Explore subagents in parallel to gather context:
Agent A — Codebase & Features
Explore the current feature set by reading:
packages/web/src/— UI components, routing, views, layout, feature flagspackages/server/— server capabilities, adapters, API surfacepackages/cli/— CLI commands and optionspackages/common/proto/— proto definitions, services, message types
Produce a summary of all user-facing features and capabilities.
Agent B — README & Screenshot Staleness
- Read
README.mdin full — note every screenshot reference, feature claim, and section - List files in
screenshots/and check their last-modified dates viagit log -1 --format="%ai" -- <file>for each - Find the oldest screenshot commit date, then run:
gh pr list --state merged --search "merged:>YYYY-MM-DD" --limit 100 --json number,title,mergedAt,labels - Summarize: which PRs are new since the last screenshot update, grouped by visual vs feature vs internal
Agent C — RFC / Roadmap / Issues
Search for forward-looking context:
- Look for RFC, roadmap, or milestone docs in the repo (
specs/,RFC*.md,ROADMAP*) - Run
gh issue list --state open --limit 50 --json number,title,labels - Run
gh milestone list --json title,description(if supported) - Identify upcoming features the README could tease as "coming soon"
Step 2: Diff Analysis
From Agent B's output, categorize the merged PRs into:
| Category | Action |
|---|---|
| Visual changes (new UI features, layout changes, new views) | Need new/recaptured screenshots |
| Feature additions (new capabilities, adapters, CLI commands) | Need README text updates |
| Internal/infra (refactors, CI, tests, tooling) | Skip — no README impact |
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 · 178 lines · 31 tokens per session scan A b2610a2af5e6
readme-refresh is a skill published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,947 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands for config.yaml and commits only after the user confirms saving; MCP servers are entries of the mcp.json files. Load…
crossreview
Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review (uncommitted work, a branch, a commit range, files, a plan or a document) out to several console code agents (Claude…
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.
rpa-bugfix
Run when the user invokes /rpa-bugfix together with a clear bug description (expected vs actual, reproduction). Reproduction test first, then fix, full test suite, short report. Will not work correctly without the bug details.