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 analiz-task-workflowgit 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/analiz-task-workflow)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/analiz-task-workflow"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/analiz-task-workflow/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/analiz-task-workflow"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/analiz-task-workflow.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.00043 | $0.01429 |
| Opus 5.5 | $0.00017 | $0.00572 |
| Sonnet 5.5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
analiz-task-workflow 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analiz Task Workflow
The system-architect normally owns analiz tasks. The human can grant a developer the analyst role for an area (Settings → Roles); when that happens, an analiz task is dispatched to you instead of the architect. Your prompt's step 1 already tells you how to tell the two cases apart: add_task_document in your tool list means you ARE the analyst for this task — follow this skill. Otherwise comment that it is misassigned and take no other action.
Which instructions apply
An analiz task is not a code task. The standing acceptance criteria (build, suite, unit test), TDD, and the code_review hand-off that the rest of your prompt and columns describe do not apply here — the deliverable is a document, not a diff. File edits are discarded: an analiz task never publishes a branch and commit_task_changes refuses it — a run that produced edits on this task type has done the wrong job on the wrong task, and those edits reach nobody.
Explore
Ground every claim in code you actually opened in this run: get_repo_tree, codebase_search, grep_code, get_symbol_skeleton, expand_symbol_context. Name the real files, symbols and interfaces you found. A document that describes a codebase you did not open is rejected.
Deliverable
ONE report, via add_task_document with format: "html", titled analiz: <YYYY-MM-DD> <topic>. Required sections, each with a stable id, in this order:
summary— what is being built and why, in 3–6 sentences, plus one decision callout stating the chosen approach.context— current state, grounded in code you read: real file paths and symbols, with what each does today.design— proposed components with exact interfaces (names, parameter and return types), data flow, error handling, the 2–3 approaches you weighed with the one-line reason the chosen one won, and out-of-scope items named explicitly.plan— numbered implementation steps (step-1,step-2, …): files to create or modify, the interfaces each step consumes and produces, and the TDD cycle with the actual test code and the command that runs it. No placeholders — "add error handling", "similar to step 2" and "TBD" are plan failures.split— one row per repository/layer: the one-line scope of its implementation task, the plan steps it owns, and its order (blocked_by/deploy_depends_on).risks— each risk with its mitigation. Open questions never go here (or anywhere in the HTML) — see "Open questions" below.
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 · 60 lines · 43 tokens per session scan A bd21c24bb7c6
analiz-task-workflow is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,429 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
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
accint-solve
Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.
ramp
Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.
paperclip-create-agent
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.