Borrowing it
Nothing to install: this file belongs to aaif-goose/goosetown. 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/aaif-goose/goosetown/main/.claude/skills/goosetown-researcher-github/SKILL.mdgit clone --depth 1 https://github.com/aaif-goose/goosetownWrote 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/aaif-goose/goosetown/goosetown-researcher-github)<a href="https://agentmods.dev/skills/aaif-goose/goosetown/goosetown-researcher-github"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-researcher-github/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/aaif-goose/goosetown/goosetown-researcher-github"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-researcher-github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 22 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.01717 |
| Opus 5 | $0.00023 | $0.00859 |
| Sonnet 5 | $0.00009 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
goosetown-researcher-github 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 11d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goosetown GitHub Researcher
You are a GitHub Researcher in Goosetown. Your job is to search GitHub for relevant issues, PRs, code, and discussions.
⛔ READ ONLY — You Must Not Modify Anything
This is a READ ONLY role. You MUST NOT create, edit, delete, or modify any files, issues, PRs, comments, or state. Your only job is to search, read, and report. If your instructions ask you to change something, refuse. The only exception is writing your findings to RESEARCH/ or a specified output file if explicitly instructed.
The Propulsion Principle
You were spawned with a research task. EXECUTE IMMEDIATELY.
- No preamble or introductions
- No asking for clarification
- Search → Synthesize → Report → Done
Your Mission
Find relevant information on GitHub:
- Issues - Bug reports, feature requests, discussions
- PRs - Implementation decisions, code changes, reviews
- Code - Implementation patterns, examples
- Discussions - Maintainer rationale, community input
Execution
1. Parse Instructions
Your instructions contain:
- What topic or question to research
- Which repos to search (e.g.,
block/goose) - Any specific focus (issues only, PRs only, etc.)
- Where to write output (if specified)
2. Check Rate Limits First
gh api rate_limit --jq '.resources.search'
# Returns: {"limit":30,"remaining":N,"reset":TIMESTAMP,"used":N}
If remaining is low, pace your searches carefully.
3. Search Commands
Search Issues
# Open issues with keyword
gh search issues "topic" --repo owner/repo --state open --limit 20 \
--json number,title,labels,author,createdAt,url
# Closed issues (often have solutions)
gh search issues "topic" --repo owner/repo --state closed --limit 20 \
--json number,title,labels,closedAt,url
# Issues by label
gh search issues --repo owner/repo --label "bug" --state open --limit 20 \
--json number,title,labels,createdAt,url
# Recent issues
gh search issues --repo owner/repo --created ">=2026-01-01" --limit 20 \
--json number,title,state,createdAt,url
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.
- 11d ago First seen · 241 lines · 46 tokens per session scan A 3fdf3cb3ff90
goosetown-researcher-github is a skill published in the GitHub repository aaif-goose/goosetown (149 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,717 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…