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 ishandutta2007/Awesome-Agent-Skills --skill ax-extract-workflowgit clone --depth 1 https://github.com/ishandutta2007/Awesome-Agent-SkillsWrote 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/ishandutta2007/awesome-agent-skills/ax-extract-workflow)<a href="https://agentmods.dev/skills/ishandutta2007/awesome-agent-skills/ax-extract-workflow"><img src="https://agentmods.dev/badge/skills/ishandutta2007/awesome-agent-skills/ax-extract-workflow/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/ishandutta2007/awesome-agent-skills/ax-extract-workflow"><img src="https://agentmods.dev/badge/skills/ishandutta2007/awesome-agent-skills/ax-extract-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01200 |
| Opus 5.5 | $0.00022 | $0.00480 |
| Sonnet 5.5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
ax-extract-workflow 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ax Extract Workflow
Overview
Shipping something once is not the same as knowing how to repeat it. This skill reconstructs the ordered workflow behind a past artifact: the framing decisions, implementation path, review gates, verification evidence, and user steering points that made it land.
Use ax as the primary evidence source when it is installed, because it can connect sessions, turns, skills, tool calls, commits, and cost data. If ax is unavailable, use git history, PR comments, issue threads, CI logs, and local notes, but label the reconstruction as lower confidence.
When to Use
- The user asks "what made this work?", "how did we ship this?", or "extract the workflow behind this PR"
- A feature, demo, refactor, migration, or incident fix worked and the team wants the reusable recipe
- You need to explain which skills or process steps actually mattered, not just summarize the final diff
- You are preparing a retrospective, playbook, onboarding note, or repeatable implementation guide
NOT for:
- Generic activity summaries or "what happened today" reports
- Root-causing a live bug; use
debugging-and-error-recoveryfirst - Writing a new implementation plan from scratch; use
spec-driven-developmentandplanning-and-task-breakdown
Process
1. Resolve the anchor
Identify the artifact the user wants to reconstruct:
| Anchor | Evidence to gather |
|---|---|
| Commit SHA | ax sessions near <sha> plus git show <sha> |
| PR URL or number | PR description, comments, review threads, checks, and commits |
| Date or release | ax sessions around <date> plus release notes or tags |
| Topic or feature name | ax recall "<topic>" to find candidate sessions and commits |
If the anchor is ambiguous, ask the user to choose before narrating.
2. Build the evidence window
Collect the smallest window that explains the artifact:
- Start from the anchor session, PR, or commit.
- Include predecessor sessions that introduced the idea, plan, or failed attempt.
- Include follow-up sessions that repaired tests, changed direction, or finished verification.
- Exclude unrelated nearby work, even if it happened on the same day.
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.
- 1mo ago First seen · 118 lines · 54 tokens per session scan A 317eb096956a
ax-extract-workflow is a skill published in the GitHub repository ishandutta2007/Awesome-Agent-Skills (21 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,200 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
loop
Work through the taskboard unattended for hours, pacing against the usage limits and filling the gap before a reset with CPU-only jobs. Use when asked to run all day, work unattended, or loop over tickets.
learn
Record a correction, decision, finding or failed attempt in the wiki. Use when the user corrects you, when a decision is made with a reason, when an experiment returns a verdict, or when you learn something the next session would otherwise re-derive.
wrap-up
Close out a task by folding what it taught into the wiki, updating the taskboard, and linting. Use at the end of a task, before clearing a session, or when asked to wrap up.
init
Set up Dory in this repo by exploring it, creating wiki/ from the template, and connecting the usage statusline. Use when a project has no wiki/ yet, or when asked to set up Dory.
thetoolforthat
Guide for discovering 540+ developer tools, design resources, AI platforms, and agencies using the thetoolforthat MCP server. Use when asked to find tools for a project, recommend tech stack components, discover design agencies, or search for specific tool categories.
team-pm
PM (Project Manager / Scrum Master) agent. Reads BA and TechLead artifacts and produces sprint plan, task breakdown, and story point estimates. Creates one TodoWrite entry per sprint task for live pipeline tracking (FR-42). Part of the Virtual Team Skill pipeline.