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/task-findernpx skills add nick-pape/grackle --skill task-findergit 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/task-finder)<a href="https://agentmods.dev/skills/nick-pape/grackle/task-finder"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/task-finder.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.00031 | $0.01245 |
| Opus 5 | $0.00015 | $0.00622 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
task-finder 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 5d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Finder — Resolve Work into (GitHub Issue + Grackle Task)
Your job is to take a piece of work — whether it's a specific issue number, a description of something to fix, or a request to pick from a backlog — and ensure it exists as both a GitHub issue and a Grackle task. You always return a resolved pair.
Repository
nick-pape/grackle
Modes
The orchestrator will invoke you in one of three modes. Determine the mode from context.
Mode A: Recommend from Backlog
Input: An epic number, label filter, or "next from backlog" instruction, plus a list of already-completed or failed tickets to skip.
- Fetch open issues via GitHub MCP matching the criteria (epic sub-issues, label filter, etc.)
- Fetch open PRs via GitHub MCP — exclude issues that already have a PR (
Closes #Nin body or issue number in branch name) - Check Grackle state — use
project_listandtask_listto find issues that already have in-progress Grackle tasks. Exclude those. - Prioritize the remaining candidates:
- Priority label:
priority:critical>priority:high> (unlabeled) >priority:low - Type:
bug>feature>refactor - Dependencies: if issue body mentions "depends on #N", it must come after #N
- Tiebreaker: lower issue number first (older)
- Priority label:
- Pick the top candidate and proceed to Resolution (below)
Mode B: Resolve a Known Issue
Input: A specific GitHub issue number (e.g., "#450").
- Verify the issue exists via GitHub MCP — fetch its title, body, labels, state
- If the issue is closed, report that and stop
- Proceed to Resolution (below)
Mode C: Create from Description
Input: A description of work that may not have a GitHub issue yet (e.g., "fix the login bug").
- Search existing issues via GitHub MCP — look for open issues with matching keywords
- If a matching issue exists, confirm it's the right one and proceed to Resolution
- If no matching issue exists, use the
/open-ticketskill to create one - Proceed to Resolution with the new issue number
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.
- 5d ago First seen · 108 lines · 31 tokens per session scan A a1547d1af9ea
task-finder 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,245 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.