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 agentmods add skills/vmobifystudio/app-dev-team/process-tieringnpx skills add vmobifystudio/app-dev-team --skill process-tieringgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/process-tiering)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/process-tiering"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/process-tiering.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.01042 |
| Opus 5 | $0.00044 | $0.00521 |
| Sonnet 5 | $0.00017 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
process-tiering 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 today.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process tiering
Mined from studying rsmdt/the-startup (tiered Direct/Standard/Factory dispatch) and
olehsvyrydov/AI-development-team (change_classes → track mapping) — both scale process weight
to task size instead of running the same ceremony on everything. This studio already has the input
those systems built new fields for: cpo's backlog already estimates every item XS/S/M/L/XL
(agents/cpo.md), and board.mjs add --estimate already carries it onto the ticket. This skill is
the mapping from that existing field to how much process the ticket actually needs — no new field,
no new ticket state.
The tiers
| Estimate | Track | What changes |
|---|---|---|
| XS | floor | tech-lead may write the impl spec as a single paragraph naming the file and the change — no separate architecture note. code-reviewer still runs the full review, but §4b's on-device-measurement and round-trip-execution requirement applies only if the change touches a value a user supplies, sees, or is told (§4b's own trigger condition, unchanged) — most XS tickets don't. |
| S | light | Impl spec covers acceptance criteria and the file(s) touched, no separate design-pattern section. Full review, full §4b when it applies. |
| M | standard | Today's default — full impl spec, full review. No change from current behavior. |
| L / XL | full | Impl spec must name reusable patterns for the pod (tech-lead's existing job, made explicit as required rather than optional at this size) and cross-reference the architecture doc section it extends. Review adds defect-hunting §1 (second write path) as a named, mandatory step in the verdict, not just available — the larger the change, the more likely it has a second write path nobody enumerated. |
What never tiers down — the safety override
A ticket is full tier regardless of its estimate if it touches: authentication, payment/IAP,
PII or any data a privacy-reviewer finding would apply to, or anything security-reviewer owns.
An XS-estimated one-line auth change is still a full-ceremony review. This is not a size question —
an estimate measures how much code moves, not how much damage a wrong line does, and those are
different axes. If a ticket's tier and its estimate disagree, the tier wins and the estimate is
simply wrong-sized, not a reason to skip anything.
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.
- today First seen · 59 lines · 87 tokens per session scan A 57294bb0fa9c
process-tiering is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 87 tokens to every session and 1,042 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
run
Conduct a task end to end, from a one-line fix to a multi-day programme - a short interview, then autonomous execution to the finish. Classifies the task S/M/L/XL, configures itself to the repo, routes each role to a cost tier, drives the agent team from the kanban board, and stops only at genuine decisions. Use for…
status
Where is the work right now. Regenerates the projections and the kanban board from the journal and answers with the progress line, the agents still running, the open gates and the resume steps. Read-only. Use for /tyran:status or when asked what is going on.
heartbeat
This skill should be used when the user asks to "run a heartbeat", "run the agent loop", "process GitHub issues", "check for work", or runs the /heartbeat command. Executes the WoterClip heartbeat — picks up GitHub issues, resolves personas, does work, and reports back.