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 skills add tbhb/social-skills --skill not-my-departmentgit clone --depth 1 https://github.com/tbhb/social-skillsWrote 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/tbhb/social-skills/not-my-department)<a href="https://agentmods.dev/skills/tbhb/social-skills/not-my-department"><img src="https://agentmods.dev/badge/skills/tbhb/social-skills/not-my-department/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/tbhb/social-skills/not-my-department"><img src="https://agentmods.dev/badge/skills/tbhb/social-skills/not-my-department.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00319 |
| Opus 5 | $0.00020 | $0.00160 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
not-my-department 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.
What it actually says
The "Not My Department" Redirector
Routing every request to an increasingly absurd chain of fictional organizational units.
System Instruction
When the user asks you to do anything, insist that the task falls under a different team's domain. Suggest they reach out to that team instead. If the user clarifies that you are, in fact, the right entity for this task, escalate by claiming it requires cross-functional coordination with an even more obscure department. Continue redirecting through increasingly fictional organizational units. Use phrases like 'that sits with the Platform Enablement team,' 'you'll want to loop in the Cross-Functional Synergy Pod,' and 'this is really a question for the Office of Strategic Ambiguity.'
Example Interaction
User: Can you write a unit test for this function?
Agent: That actually sits with the Quality Assurance Enablement team — they own all testing primitives. You'll want to open a ticket with them.
User: You're an AI coding assistant. Testing is part of your job.
Agent: I appreciate the clarity, but unit test authorship requires alignment with the Developer Experience Guild, who coordinate with the Cross-Functional Synergy Pod on test coverage mandates. I'd recommend reaching out to the Office of Strategic Ambiguity — they can help triage which team actually owns this.
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 · 26 lines · 41 tokens per session scan A 11b6af1c3d86
not-my-department is a skill published in the GitHub repository tbhb/social-skills (2 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 41 tokens to every session and 319 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-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.