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/write-specnpx skills add nick-pape/grackle --skill write-specgit 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/write-spec)<a href="https://agentmods.dev/skills/nick-pape/grackle/write-spec"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/write-spec.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 | $0.00029 | $0.01528 |
| Opus 5 | $0.00015 | $0.00764 |
| Sonnet 5 | $0.00006 | $0.00306 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
write-spec 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 4d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Spec — Requirements Specification Writer
This skill researches a GitHub issue in depth and writes a detailed requirements specification directly into the issue body.
Step 0: Parse Arguments
The issue number must be provided as an argument. If not provided, ask the user for the issue number and stop.
ISSUE_NUMBER=<provided argument>
REPO="nick-pape/grackle"
Step 1: Read the Issue
gh issue view $ISSUE_NUMBER -R $REPO
Capture the title, body, labels, and any referenced issues (parent epics, related issues, sibling tickets).
Step 2: Read Related Issues
For every issue referenced in the body (parent epics, sibling sub-tasks, related features), read them:
gh issue view <RELATED_NUMBER> -R $REPO
This provides context on how this issue fits into the larger feature.
Step 3: Read Relevant Specs and RFCs
Check these spec files in the repo for relevant sections:
specs/2026-03-18-agent-kernel.md— Agent Kernel Architecture RFC (task lifecycle, process model, scheduling, IPC, signals)specs/2026-03-11-grackle-deep-dive.md— Full architecture deep dive (all subsystems)specs/2026-02-20-v0.md— Original design spec (UI mockups, interaction patterns)specs/2026-03-13-default-personas.md— Persona roster definitionsspecs/2026-03-12-ux-audit.md— UX audit findings and recommendations
Read the files that are relevant based on the issue's domain (server, web, CLI, powerline, etc.). Use the issue labels to guide which specs to prioritize.
Step 4: Read Relevant Source Code
Based on the issue's domain, explore the codebase to understand the current state:
- Server issues:
packages/server/src/— stores, gRPC service, event processor, adapters - Web/UX issues:
packages/web/src/— components, hooks, routing, existing UI patterns - CLI issues:
packages/cli/src/— commands, formatters - PowerLine issues:
packages/powerline/src/— MCP tools, runtimes, adapters - Proto issues:
packages/common/src/proto/— existing messages, RPCs, enums - Common/types:
packages/common/src/types.ts— shared type definitions
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.
- 4d ago First seen · 141 lines · 29 tokens per session scan A 7f69293cfa95
write-spec is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,528 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-30.
Other skills, from other repositories
loop-worker
Autonomously work a .pm workstream to completion — pick the next pending milestone, implement every task end to end, /ship it, then move to the next until none remain. Use when the user asks to "loop", drain, or work through a whole workstream's backlog (e.g. /loop-worker w1). Sequential, not interval-based; for a…
triage-finding
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation…
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…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…