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/britt/agent-skills/dependency-mappingnpx skills add britt/agent-skills --skill dependency-mappinggit clone --depth 1 https://github.com/britt/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/britt/agent-skills/dependency-mapping)<a href="https://agentmods.dev/skills/britt/agent-skills/dependency-mapping"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/dependency-mapping.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.00045 | $0.01579 |
| Opus 5 | $0.00023 | $0.00790 |
| Sonnet 5 | $0.00009 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
dependency-mapping 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 3d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Mapping Skill
Generate Mermaid flowcharts that visualize GitHub issue dependencies, blocking relationships, and critical paths through the project.
When to Use
Activate this skill when:
- User asks "show me the dependencies", "map the issue dependencies"
- User wants to see which issues block others
- During sprint planning to identify critical path
- After issue decomposition to visualize relationships
CRITICAL: Mermaid Syntax Rules
NEVER use parentheses in node labels
Parentheses break GitHub rendering.
WRONG:
flowchart LR
I1[#1 Setup (init)]
CORRECT:
flowchart LR
I1[#1 Setup - init]
Issue Node Naming Convention
Use consistent naming for issue nodes:
flowchart LR
I201[#201 Setup auth module]
I202[#202 Implement login]
I203[#203 Add password reset]
Format: I<number>[#<number> <short title>]
Dependency Graph Patterns
Linear Dependencies
Issues that must be done in sequence:
flowchart LR
I1[#1 Setup project] --> I2[#2 Create database]
I2 --> I3[#3 Add API endpoints]
I3 --> I4[#4 Integration tests]
Parallel Work
Issues that can be done simultaneously:
flowchart TB
I1[#1 Setup project]
I1 --> I2[#2 Frontend setup]
I1 --> I3[#3 Backend setup]
I2 --> I4[#4 Integration]
I3 --> I4
Complex Dependencies
Multiple blocking relationships:
flowchart TB
subgraph Foundation
I1[#1 Project setup]
I2[#2 Database schema]
end
subgraph Features
I3[#3 User auth]
I4[#4 User profile]
I5[#5 Settings page]
end
subgraph Integration
I6[#6 End-to-end tests]
end
I1 --> I2
I1 --> I3
I2 --> I3
I3 --> I4
I3 --> I5
I4 --> I6
I5 --> I6
Critical Path Highlighting
Emphasize the longest dependency chain:
flowchart LR
I1[#1 Setup]
I2[#2 Database]
I3[#3 Auth]
I4[#4 API]
I5[#5 Tests]
I1 ==> I2
I2 ==> I3
I3 ==> I4
I4 ==> I5
I1 --> I6[#6 Docs]
style I1 fill:#f96
style I2 fill:#f96
style I3 fill:#f96
style I4 fill:#f96
style I5 fill:#f96
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.
- 3d ago First seen · 249 lines · 45 tokens per session scan A 213906fae010
dependency-mapping is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 1,579 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
okx-task-watch
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via okx-a2a user watch (also drains backlog of past/missed/unread events on entry) plus…
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.