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 itdove/devaiflow --skill daf-issue-topo-sortgit clone --depth 1 https://github.com/itdove/devaiflowWrote 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/itdove/devaiflow/daf-issue-topo-sort)<a href="https://agentmods.dev/skills/itdove/devaiflow/daf-issue-topo-sort"><img src="https://agentmods.dev/badge/skills/itdove/devaiflow/daf-issue-topo-sort/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/itdove/devaiflow/daf-issue-topo-sort"><img src="https://agentmods.dev/badge/skills/itdove/devaiflow/daf-issue-topo-sort.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.03515 |
| Opus 5.5 | $0.00007 | $0.01406 |
| Sonnet 5.5 | $0.00003 | $0.00703 |
| Haiku 4.5 | $0.00002 | $0.00351 |
Grade A, and why
daf-issue-topo-sort 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Topology Sort
Topologically sort issues by explicit dependencies AND file conflict avoidance. Produces an ordered work plan with concurrent groups.
Usage
/daf-issue-topo-sort [--repo owner/repo] [--label <label>] [--parent <JIRA-KEY>]
GitHub: /daf-issue-topo-sort --repo owner/repo --label v1.0
GitHub (current repo): /daf-issue-topo-sort --label v1.0
JIRA: /daf-issue-topo-sort --parent PROJ-123
If no arguments given, ask the user which mode (GitHub or JIRA) and the required parameters.
Step 1: Gather Issues
GitHub
gh issue list --repo <repo> --label <label> --state open --json number,title,body,url --limit 100
If --repo not provided, use current repository (auto-detected from git remote).
For each issue, also fetch comments:
gh issue view <number> --repo <repo> --json comments --jq '.comments[].body'
JIRA
Use MCP JIRA tools to fetch child issues of the parent:
mcp__mcp-atlassian__jira_search(
jql="parent = <PARENT-KEY> AND status != Done ORDER BY key ASC",
fields="summary,status,description,comment,issuelinks"
)
For each issue, also fetch full details including comments:
mcp__mcp-atlassian__jira_get_issue(issue_key=<KEY>, fields="*all", comment_limit=50)
Output of this step: A list of open issues only, each with: key/number, title, body/description, comments, and (for JIRA) existing issue links. Closed/done issues must never appear in this list or any subsequent step.
Step 2: Analyze Each Issue
For each issue, extract two things:
2a. Explicit Dependencies
Scan issue body AND all comments for dependency patterns (case-insensitive):
| Pattern | Meaning |
|---|---|
depends on #X / depends on PROJ-X |
This issue depends on X |
after #X / after PROJ-X |
This issue should come after X |
needs #X first / needs PROJ-X first |
This issue needs X completed first |
blocked by #X / blocked by PROJ-X |
This issue is blocked by X |
requires #X / requires PROJ-X |
This issue requires X |
prerequisite: #X / prerequisite: PROJ-X |
X is a prerequisite |
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 · 387 lines · 17 tokens per session scan A ff1d2a6287b0
daf-issue-topo-sort is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 3,515 once invoked, about $0.0001 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.