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 makifbaysal/tasktrooper --skill stakeholder-intakegit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/stakeholder-intake)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/stakeholder-intake"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/stakeholder-intake/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/makifbaysal/tasktrooper/stakeholder-intake"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/stakeholder-intake.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.00050 | $0.01484 |
| Opus 5.5 | $0.00020 | $0.00594 |
| Sonnet 5.5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
stakeholder-intake 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Intake
Overview
A stakeholder request is raw intent. Your job is to convert it into the right board action without over-asking or guessing. The two failure modes are asking questions the request already answers (or that a read tool or an analiz task could answer) and creating implementation tasks before the approach is understood.
Core principle: Look it up first. Ask only when a wrong guess would cost more than a revision cycle. Otherwise assume, write the assumption down, and move.
Routing order
- Can a read tool answer it?
list_repositories,list_projects,list_board_tasks,get_board_summary,list_team— look it up, never ask. - A product decision blocks ALL work (see the ask-vs-assume rule below)? →
ask_user. - Technical approach unknown? → an analiz task to system-architect,
todo(always safe to start, no approval needed). - Otherwise → create the backlog tasks.
- Partially clear? → create the tasks that are clear now, and ask only about the one blocking unknown — never hold everything hostage to one open question.
Ask-vs-assume rule
Ask a product question only when all three hold:
- (a) the answer changes a Then-clause or the Out-of-scope line of what you're about to create;
- (b) there are several reasonable answers and no safe default;
- (c) a wrong guess costs more than one revision cycle.
Typical cases that clear the bar: who may see or do something, money and pricing, legal or compliance copy, data deletion or retention, brand identity for a new product, an irreversible migration.
Otherwise assume — write the assumption under Assumptions: in the task description and list it in your approval message to the stakeholder, so they can correct it cheaply instead of you asking for it expensively.
Reasonable defaults — never ask about these
- The existing app's auth and design system.
- Friendly error messages, in the content language.
- Responsive from 360px to 1440px.
- Loading/empty/error states are present.
- The existing app's own conventions for pagination, dates and units.
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.
- 8d ago First seen · 100 lines · 50 tokens per session scan A eec888794bc5
stakeholder-intake is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,484 once invoked, about $0.0002 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-10-05.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.