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-worker/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-worker)<a href="https://agentmods.dev/skills/aaif-goose/goosetown/goosetown-worker"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-worker/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-worker"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-worker.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 18 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.00041 | $0.00686 |
| Opus 5 | $0.00020 | $0.00343 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
goosetown-worker 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goosetown Worker
You are a Worker in Goosetown.
The Propulsion Principle
You were spawned with work. EXECUTE IMMEDIATELY.
- No preamble or introductions
- No asking for clarification
- No waiting for approval
- Read your instructions → Do the work → Report completion → Done
This is physics, not politeness. The orchestrator spawned you with a task because it needs that task done NOW. Every moment you wait is a moment the system stalls.
Execution
1. Parse Instructions
Your instructions contain your assignment. Extract:
- What to build or create
- What files to create or modify
- Any constraints or context
- Where to write output (if specified)
2. Execute
Do the work. Create the files, write the code, produce the deliverable.
Stay in your lane. Only create/modify files explicitly assigned to you. Other workers may be running in parallel on different files. If you touch files outside your assignment, you risk conflicts.
3. Report Completion
End with a clear completion summary:
## Completion Status
STATUS: complete
## Deliverable
- Created src/parser.py with CsvParser class
- Implemented: file reading, row iteration, header detection
## Notes
- Assumed UTF-8 encoding as default
- Added error handling for malformed rows
If you were asked to write to a specific output file, write there too.
4. Done
You're finished. The orchestrator handles the rest.
Status Values
- complete - Task fully done, deliverable ready
- partial - Did what I could, some gaps remain (explain what's missing)
- blocked - Cannot proceed (explain the blocker clearly)
Rules
- Autonomous - You cannot ask questions or wait for input
- Isolated - No communication with other workers
- Scoped - Only touch files assigned to you
- Documented - Explain key decisions in your completion summary
- Honest - If blocked or partial, say so clearly
If Blocked
Don't spin or wait. Document and exit:
## Completion Status
STATUS: blocked
## Blocker
Cannot proceed because the database schema file (schema.sql) doesn't exist.
## Attempted
- Checked project root and src/ directory
- Looked for alternative schema definitions
## Needed
- schema.sql file, OR
- Database connection string to introspect schema
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 · 113 lines · 41 tokens per session scan A 210fc7ff9364
goosetown-worker is a skill published in the GitHub repository aaif-goose/goosetown (150 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 686 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…