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/jsuvic/agent-profile/implement-nextnpx skills add jsuvic/agent-profile --skill implement-nextgit clone --depth 1 https://github.com/jsuvic/agent-profileWhat 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.00031 | $0.00761 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
implement-next 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Next
Purpose
Advance exactly one ready task from the TASKS.md ledger through a single implementation cycle, using its persisted issue brief as context. One invocation advances at most one task; it never iterates. Repeat the command for the next task.
Preconditions
TASKS.mdexists and is an index-only ledger whose rows link to issue briefs.- If
TASKS.mdis missing or contains noreadytask, stop and report the ledger state; do not invent work.
Flow
- Read
TASKS.mdand select the first task in stateready.- Stop at a
human-gatetask and explain the approval it needs; do not proceed past it. - Skip
blockedandsequencedtasks; they are not ready. - If no
readytask exists, stop and report.
- Stop at a
- Mark the selected task
in-progressinTASKS.mdthrough the client's write-approval flow. - Load the linked issue brief and run
subagent-driven-changewith the brief as Fresh Context. Its owner runscode-quality-reviewerbeforechange-risk-reviewer; initiate or resume the closed change-risk handoff and report its current state, but do not independently invoke another review, redefine budgets, or reset counters. - Mark the task
doneonly after the owner returns a validated terminalCLEANhandoff and required tests run green. Validate the closedChangeRiskOrchestrationStateV1record; its snapshot matches the current snapshot (modulodocs/review-learning/) and its terminal status isCLEAN. Do not infer completion from free-form prose or an unvalidated status. The next task requires a new invocation. - If the validated handoff reports
NO_PROGRESSorNEEDS_HUMAN_REVIEW, report that outcome and its required escalation; do not mark the taskdoneor start another review. Keep the task out ofdoneuntil a human resolves the escalation.
Failure Path
Stop and report BLOCKED when any of these holds:
implementerreturnsBLOCKEDorNEEDS_CONTEXT,- a review finding cannot be resolved within the brief's scope,
- GREEN is unreachable within the brief's declared seam.
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 First seen · 52 lines · 31 tokens per session scan A 0bcc35047cdb
implement-next is a skill published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 9d ago), licensed Apache-2.0. It adds 31 tokens to every session and 761 once invoked, about $0.0002 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
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
speckit.status
Progress Dashboard - Displays project progress status.
speckit.taskstoissues
Issue Tracker Syncer - Synchronize tasks.md to issue tracker.
create-issue
Create a GitHub issue using the appropriate template.
feature-to-work-packets
Use when decomposing an approved specification into ordered work packets with a file owner, exact paths, single-writer ownership, dependencies, risks, evidence, and verification commands.