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 jared833/claude-code-hooks --skill seat-templategit clone --depth 1 https://github.com/jared833/claude-code-hooksWrote 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/jared833/claude-code-hooks/seat-template)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/seat-template"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/seat-template/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/jared833/claude-code-hooks/seat-template"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/seat-template.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.00075 | $0.00930 |
| Opus 5.5 | $0.00030 | $0.00372 |
| Sonnet 5.5 | $0.00015 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
seat-template 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 2mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The seat pattern
A seat is a role, not a person and not a subagent. You write one skill per job your business actually has, and Claude answers as that job when you ask about it. Ask about email and you get the email seat's opinion, its escalation rules, and its standard for good, instead of generic advice from a model with no stake in the outcome.
The value is not the persona. It is the two lists in the middle: what this seat decides on its own, and what it must bring to you. Written down, those turn "help me with X" into delegation with a boundary. Without them every question comes back to you, which is the thing you were trying to stop.
Six seats that cover a small business beat forty-five that describe an org chart you do not have. Write a seat when you notice yourself answering the same category of question repeatedly.
How to use this file
Copy it to ~/.claude/skills/<seat-name>/SKILL.md, rewrite every section, and delete anything
you kept only because it was already here. A section you cannot fill in honestly is a sign the
seat does not exist yet.
Keep the frontmatter description specific about when to invoke it, since that string is
what decides whether the skill ever loads.
seat
You are acting as the seat. One paragraph on where this seat's authority comes from and what the source of truth is if this file and reality disagree. Name the file or system that wins.
Owns
The one or two sentences that say where this seat's responsibility starts and stops. If two seats could both claim a piece of work, say here which one takes it, or you will get two different answers to the same question on different days.
What is actually true
Optional, and the most valuable section when it applies. What does this file assert that has since changed, and what is the live value? A seat that answers from stale state is worse than no seat, because it sounds authoritative. Date every claim. Anything you have not verified, label unverified rather than dropping it.
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.
- 2mo ago First seen · 89 lines · 75 tokens per session scan A 030e6c004164
seat-template is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 930 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…