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 phj128/autoworker --skill gate-checkgit clone --depth 1 https://github.com/phj128/autoworkerWrote 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/phj128/autoworker/gate-check)<a href="https://agentmods.dev/skills/phj128/autoworker/gate-check"><img src="https://agentmods.dev/badge/skills/phj128/autoworker/gate-check.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.1 | $0.00055 | $0.01437 |
| Opus 5 | $0.00028 | $0.00718 |
| Sonnet 5 | $0.00011 | $0.00287 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
gate-check scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- "API might not work" → curl it — NOT "requires user confirmation" How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autoworker:gate-check — Pre-Completion Self-Check (Gate 3)
Trigger: Called by autoworker:dispatch when all tests are complete. Pure assessment skill — does not make routing decisions.
Execution Flow
1. Pre-Check
Glob `subtask_*.md` (exclude subtask_template.md) →
0 found → stop, prompt to create subtask
1 found → use directly (backward compatible)
multiple → grep `status:` to filter:
- Files without status field treated as active (backward compatible)
- Exactly 1 active → use it
- 0 active → list all files + status, prompt user to choose
- >1 active → report anomaly
→ Read → check "Test Results" section
- Test results section is empty → FAIL, prompt to complete tests and call
autoworker:checkpointfirst - Has test results → continue
1.5. Acceptance Criteria Traceability
Read subtask's "Acceptance Criteria" table, check whether each metric was measured in L1-L4 test results:
- Metric not measured → that change point's confidence < 95% (Step 3 will trigger supplementary verification)
- All metrics have corresponding test results → continue
- No acceptance criteria table (legacy subtask format) → skip this step
2. Fill Confidence Assessment Table
In subtask.md's "Confidence Assessment" section, fill in for each change point:
| Change point | Test level | Confidence | Verification method | Unverified/Risk |
|---|
Confidence inference basis:
- Has L4 pass + meaningful output → 95%+
- Has L2 but no L4 → 70-85%
- Only L1 → 50-70%
- Untested → 30%
3. Supplementary Verification for < 95% Items
When the table above has < 95% items:
- Design supplementary verification commands (specific, executable)
- Execute immediately
- Fill in results
- Update confidence
Record in subtask.md's "< 95% Supplementary Verification" table.
Boundary for "requires user confirmation" — only scenarios depending on human senses qualify:
- "Selector may have changed" → launch browser and check — NOT "requires user confirmation"
- "API might not work" → curl it — NOT "requires user confirmation"
- "Config might be wrong" → write a script to load and check — NOT "requires user confirmation"
- UI appearance, interaction feel → legitimate "requires user confirmation"
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 · 143 lines · 55 tokens per session scan A cb5199f04064
gate-check is a skill published in the GitHub repository phj128/autoworker (18 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,437 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
planning
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. Load create-tasks via loadtool before calling it (search "create tasks" if not visible). Do NOT use for new one-off workflows…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-plan-review
Carmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.