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/cunhaax/ai-workflow/featurenpx skills add cunhaax/ai-workflow --skill featuregit clone --depth 1 https://github.com/cunhaax/ai-workflowWrote 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/cunhaax/ai-workflow/feature)<a href="https://agentmods.dev/skills/cunhaax/ai-workflow/feature"><img src="https://agentmods.dev/badge/skills/cunhaax/ai-workflow/feature.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.00037 | $0.03187 |
| Opus 5 | $0.00018 | $0.01594 |
| Sonnet 5 | $0.00007 | $0.00637 |
| Haiku 4.5 | $0.00004 | $0.00319 |
Grade A, and why
feature 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 4d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feature — AI-Assisted Development Lifecycle
Activate this skill for non-trivial features or changes to run the full structured development workflow: plan → critique → implement → test → code-review → QA → PR.
Workflow
Step 1 — Draft, critique, and approve the plan
Preconditions — check the branch first. The workflow assumes the human
started this session on a fresh feature branch: the code review (Step 4)
diffs against the default branch (named in AGENTS.md → Commands) and
Step 9 opens a PR targeting it, neither of which works from the default
branch itself. If the session is on the default branch, STOP and ask the
user to create a feature branch — you may not create or switch branches
yourself (Rule 3 in AGENTS.md).
Enter plan mode now, before drafting. Plan mode is a structural commitment: while in plan mode the harness blocks edit tools, so the workflow cannot skip the approval gate even if the agent is tempted to inline the plan and proceed. Stay in plan mode through steps 1a, 1b, and 1c. Exit plan mode only in step 1c, after the user approves.
Step 1a — Draft the plan
Invoke the planner sub-agent to draft an implementation plan. Pass the
user's prompt verbatim — including any reference to docs or links. The
planner will fetch all external specs with its own tools (it has WebFetch
for URLs) and return the plan as markdown text.
Do not use tools directly — always delegate to the planner sub-agent, regardless of which platform you are running on.
Step 1b — Critique the plan
Invoke the plan-critic sub-agent with the draft plan as input. The critic
will apply pre-mortem, inversion, load-bearing assumption analysis, and
consistency checks against ADRs and product docs, and return the critique
as markdown text.
Skip this step ONLY if the change qualifies as trivial under ALL of:
- diff is plausibly under ~50 lines of non-test code,
- touches none of the project's sensitive areas (the Sensitive Areas
section in
AGENTS.mdis the canonical list), - introduces no new public endpoints, no new persisted fields, no new external dependencies,
- AND the user explicitly said "skip the critic" (or equivalent) in this session.
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.
- 4d ago First seen · 278 lines · 37 tokens per session scan A ce4b34d26ccf
feature is a skill published in the GitHub repository cunhaax/ai-workflow (5 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 3,187 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
golden-jupyter-dir
Use when testing the goldenjupyterdir golden build.
golden-man-kw
Use when testing the man golden build.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
golden-rss
Use when testing the rss golden build.
golden-chat-topics
Use when testing the goldenchattopics golden build.
golden-chat-single
Use when testing the goldenchatsingle golden build.