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 | $0.00027 | $0.00600 |
| Sonnet 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 11d 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.
- 11d 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 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,200 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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.
team-list
Utility skill. Lists all projects under the projects/ directory and shows which Virtual Team pipeline phases have been completed for each project.
discover-tasks
Use when user asks to "discover tasks", "find next task", "prioritize issues", "what should I work on", or "list open issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
drift-analysis
Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.
repo-intel
Use when user asks to "run repo intel", "generate repo map", "analyze repo", "query hotspots", "check ownership", or "bus factor". Unified static analysis - git history, AST symbols, project metadata.