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/launch-grackle/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/launch-grackle)<a href="https://agentmods.dev/skills/nick-pape/grackle/launch-grackle"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/launch-grackle/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/launch-grackle"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/launch-grackle.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.01174 |
| Opus 5.5 | $0.00000 | $0.00470 |
| Sonnet 5.5 | $0.00000 | $0.00235 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade C, and why
launch-grackle scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$GRACKLE_HOME" How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Grackle for Testing
Launches an isolated Grackle server instance with ephemeral ports and a branch-specific home directory. Prevents agents from conflicting with each other or destabilizing the user's real database.
Invocation
/launch-grackle
Prerequisites
rush buildmust have been run (server runs fromdist/)- If you only changed one package,
rush build -t @grackle-ai/<package>is sufficient
Launch
Run the launch script from the repo root as a single Bash call:
bash .claude/scripts/launch-grackle.sh
The script finds 4 free ports, creates a branch-specific home directory, starts the server, waits for it to be ready, reads the API key, generates a pairing code, and prints all connection details. It also writes $GRACKLE_HOME/env.sh for use in follow-up calls.
Using the env in follow-up bash calls
Each subsequent bash call can source the env file to restore all variables:
BRANCH="$(git rev-parse --abbrev-ref HEAD)"
SAFE_BRANCH="$(printf '%s' "$BRANCH" | tr '/' '-' | tr -c 'a-zA-Z0-9_-' '_')"
source "/tmp/grackle-${SAFE_BRANCH}/env.sh"
# Now $GRPC_PORT, $WEB_PORT, $GRACKLE_API_KEY, $SERVER_PID, etc. are available
Pairing / Auth Flow
The web UI uses pairing-code authentication — it does NOT accept the API key directly. You must complete pairing before the browser can access the UI.
How pairing works:
- The server generates a 6-character pairing code
- A browser hits
/pair?code=XXXXXX— this redeems the code and sets a session cookie - All subsequent web requests use the session cookie (valid for 24 hours)
- Without a valid session cookie, the browser is redirected to
/pair - Pairing codes expire after 5 minutes. Run
grackle pairto generate a new one.
For Playwright MCP testing:
- You MUST navigate to the pairing URL first before testing the web UI
- Navigate to
$PAIRING_URL— this will set the session cookie and redirect to/ - After that, the browser has a valid session and you can navigate freely
- If the pairing code has expired, source the env file (above) then generate a new one:
GRACKLE_URL="http://127.0.0.1:$GRPC_PORT" GRACKLE_API_KEY="$GRACKLE_API_KEY" grackle pair
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 · 97 lines · 0 tokens per session scan C f30789890c77
launch-grackle is a skill published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,174 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…