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 HirogaKatageri/hirokata --skill shiftgit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/shift)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/shift"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/shift/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/shift"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/shift.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 21 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00126 | $0.07431 |
| Opus 5.5 | $0.00050 | $0.02972 |
| Sonnet 5.5 | $0.00025 | $0.01486 |
| Haiku 4.5 | $0.00013 | $0.00743 |
Grade A, and why
shift 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 29d 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 — 596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guild Shift — working the board while you are away
Run until the next gate, then stop and notify.
That one sentence is the whole design. A requirement's work is cut into segments by its two gates, and a segment is by definition everything that can run without asking anyone anything. So the segment boundary and the stop boundary are the same line, and an unattended shift needs no separate notion of "how far may it go" — it goes to the next gate. Then it stops, records why, and waits.
Load guild:warehouse before the first turn. Every query on this page is raw SQL against
.guild/guild.db, and the six rules in that skill — hex transport, PRAGMA foreign_keys, never
parsing -m list positionally, reading views instead of re-deriving them, RETURNING on every
mutation, errors arriving on stdout — apply to every one of them. At 3am there is nobody to
notice a swallowed error.
This skill is guild:check-in with the human taken out of the middle. The dispatch protocol is
unchanged and is not restated here — how a batch is run, how an agent is spawned, and how a
result is recorded all live in guild:check-in, and you follow it exactly. What a shift adds is
a budget, a failure policy that never stops to ask, a commit per completed task, and a hard stop
at the gate.
Before you walk away — what you are authorizing
Say this out loud, before the first turn, so the user knows what they are leaving running. It is not a formality: they are handing an unsupervised process their working tree.
| A shift MAY | A shift MAY NOT |
|---|---|
| Claim any open, dependency-satisfied bounty | Approve a gate, or reject one |
| Run whole segments; compile and run workflows | Proceed past an unresolved gate |
| Retry a failed task once, with a fresh agent | Create a gate, or drop one |
Mark tasks failed or blocked, and move on |
Mark a requirement done past an unresolved gate |
| File bugs and review findings | Delete anything, or rewrite history |
Append to work_log and review_finding |
Push to a remote |
Commit per completed task, on guild/REQ-NNN |
Commit to the default branch |
| Change goals, projects or priorities | |
| Create a guild member |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 29d ago Changed · -37 lines a7a0135b78db
- 1mo ago Changed · -2 lines fa97fec37220
- 1mo ago Changed 0453b16c4d19
- 1mo ago First seen · 635 lines · 126 tokens per session scan A b81727d8aa25
shift is a skill published in the GitHub repository HirogaKatageri/hirokata (6 stars, last pushed 13d ago), licensed MIT. It adds 126 tokens to every session and 7,431 once invoked, about $0.0005 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-09-04.
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.
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.
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.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.