Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add HirogaKatageri/hirokata/plugin install guildWrote 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/hirogakatageri/hirokata/new-requirement)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/new-requirement"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/new-requirement/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/hirogakatageri/hirokata/new-requirement"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/new-requirement.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.00144 | $0.08727 |
| Opus 5 | $0.00072 | $0.04364 |
| Sonnet 5 | $0.00029 | $0.01745 |
| Haiku 4.5 | $0.00014 | $0.00873 |
Grade A, and why
new-requirement 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 2d 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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Requirement — Add Work to the Guild
Run the project-manager and strategist through a live interview with the user, then hand the board a fully-planned requirement: the requirement itself, an implementation plan, every ticket needed to build it, and the execution graph that says what runs when. Unlike the rest of the guild's pipeline, none of this is ticket-dispatched — you (the orchestrator) spawn both agents directly and moderate the conversation until the user says it's done.
Load guild:warehouse first. There is no guild CLI: tursodb is the tool and every write
below is SQL. The canonical statements — creating a requirement, a plan, a ticket with
its capabilities, instantiating a graph — are in references/queries.md; copy from there rather
than improvising.
Where this skill stops: gate-plan
This skill plans. It does not build. It ends by presenting the plan at gate-plan — the
first of the guild's two gates, and the whole point of the gate model:
The plan is the cheapest place to change your mind. Approving it costs one decision and redirects everything downstream. After that, the guild runs to completion without stopping, and the problems it finds are collected and judged together at
gate-repairs.
So the last thing you do here is put the plan in front of the guild master and record their
answer (Step 7). Nothing is dispatched, nothing is implemented, no ticket leaves todo until
that approval exists. If they approve, /guild:check-in runs the first batch. If they don't,
the requirement sits with a pending gate and the board is unchanged — which is exactly what a
plan gate is for.
Only you can ask. Subagents cannot call AskUserQuestion, which is why a gate can never
live inside a dispatched workflow and why this skill — the orchestrator session — is where it
happens.
Arguments
| Argument | Description |
|---|---|
title |
Short title for the requirement (e.g., "User Authentication") |
description |
Brief description of what's needed |
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.
- 2d ago Changed c674fdc78725
- 3d ago Changed · +5 lines d4959230dc25
- 7d ago Changed · +426 lines · +35 tokens per session b153a0aef104
- 11d ago First seen · 215 lines · 109 tokens per session scan A 8d9677a76432
new-requirement is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 144 tokens to every session and 8,727 once invoked, about $0.0007 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
crm-management
Use when an internal 101 goal must manage CRM pipelines, stages, deals, or distribution rules through the current CRM API.
estimate-management
Use when an internal 101 goal must find, read, create, or edit one or many estimates through the existing event API, including sourced or manual positions and their dates.
project-management
Use when an internal 101 goal must create or edit a project, select its customer or price list, manage project expense categories, or copy category settings from another project.
task-management
Use when an internal 101 goal must list, read, open, update, or comment on tasks, including the interactive task detail widget.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…