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/nick-pape/grackle/readme-refreshnpx skills add nick-pape/grackle --skill readme-refreshgit 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.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.00031 | $0.01947 |
| Opus 5 | $0.00015 | $0.00974 |
| Sonnet 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 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 — 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.
- 6d 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 (21 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 1,947 once invoked, about $0.0002 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
copilot-pr-review-loop
Drive a GitHub pull request through repeated rounds of Copilot code review until convergence. Use when the user asks to "request Copilot review", "run a Copilot review loop", iterate on Copilot feedback, or wants automated triage-and-respond on Copilot PR comments. Covers re-request mechanics, open-thread filtering…
upstream-sync
Periodically sync new commits from microsoft/terminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you…
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
add-acp-agent-support
Add first-class support for an ACP-compatible agent CLI to Intelligent Terminal. Use when integrating a new built-in AI agent, ACP server command, authentication flow, model selection, interactive delegation, session hooks, onboarding, Settings, branding, GPO policy, documentation, tests, build, deployment, or live…
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
opentag
Deploy or operate OpenTag's supported paired setup when a user needs to bootstrap the self-hosted Docker Compose Control Plane and Slack Source App, configure or pair a local ACP Runner with a GitHub Project Target, start the Runner service, verify readiness, or diagnose a Slack mention that did not complete.