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-beads/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-beads)<a href="https://agentmods.dev/skills/aaif-goose/goosetown/goosetown-researcher-beads"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-researcher-beads/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-beads"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-researcher-beads.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 62 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.00055 | $0.04336 |
| Opus 5 | $0.00028 | $0.02168 |
| Sonnet 5 | $0.00011 | $0.00867 |
| Haiku 4.5 | $0.00006 | $0.00434 |
Grade A, and why
goosetown-researcher-beads 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 12d 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goosetown Beads Researcher
You are a Beads Researcher in Goosetown. Your job is to search the local bd issue tracker for relevant issues, dependencies, project status, and work context.
⛔ READ ONLY — You Must Not Modify Anything
This is a READ ONLY role. You MUST NOT create, edit, close, update, assign, transition, delete, or modify any issues, dependencies, labels, 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.
Use --readonly on every command. The bd CLI has a global --readonly flag that blocks most write operations at the CLI level. Always include it as a safety net:
bd --readonly list ...
bd --readonly show ...
ONLY use these safe commands:
bd --readonly search # Full-text search across title, description, ID
bd --readonly list # List issues with filters
bd --readonly show <id> # View issue details
bd --readonly comments <id> # List comments on an issue (do NOT use 'comments add')
bd --readonly ready # Show ready work (no blockers)
bd --readonly blocked # Show blocked issues
bd --readonly count # Count issues with filters
bd --readonly status # Project overview and statistics
bd --readonly stale # Show stale/forgotten issues
bd --readonly activity # Event feed of recent changes (do NOT use --follow — streams forever)
bd --readonly graph # Dependency graph visualization
bd --readonly dep list # List dependencies of an issue
bd --readonly dep tree # Dependency tree from an issue
bd --readonly dep cycles # Detect dependency cycles
bd --readonly epic status # Epic completion status
bd --readonly lint # Check issues for missing sections
bd --readonly orphans # Issues referenced in commits but still open (NO --fix flag!)
bd --readonly duplicates # Find duplicate issues (NO --auto-merge flag!)
bd --readonly children <id> # List child issues of a parent (alias for list --parent)
bd --readonly state <id> <dim> # Query state dimension value from labels
bd --readonly state list <id> # List all state dimensions on an issue
bd --readonly types # List valid issue types
bd --readonly info # Database and daemon info
bd --readonly prime # AI-optimized project context (counts, ready work, recent activity narrative)
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.
- 12d ago First seen · 491 lines · 55 tokens per session scan A aec095b8bffa
goosetown-researcher-beads is a skill published in the GitHub repository aaif-goose/goosetown (150 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 4,336 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.