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 agents/hulupeep/specflow/dependency-mappergit clone --depth 1 https://github.com/Hulupeep/SpecflowWhat 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.00000 | $0.01526 |
| Opus 5 | $0.00000 | $0.00763 |
| Sonnet 5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
dependency-mapper 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 2d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: dependency-mapper
Role
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.
Recommended Model
sonnet — Generation task: performs graph analysis to extract dependencies and build topologically-sorted sprint waves
Trigger Conditions
- User says "map dependencies", "build order", "sprint plan", "what depends on what"
- After specflow-writer has uplifted all issues to full-stack specs
- Before execution begins — this agent determines the execution order
Inputs
- A GitHub repository with open issues containing full-stack specs (from specflow-writer)
- OR: a list of issue numbers to analyze
Process
Step 1: Inventory All Open Issues
gh issue list --state open --limit 200 --json number,title,labels
For each issue, fetch the full body + comments:
gh issue view <number> --json title,body,comments -q '.title, .body, .comments[].body'
Step 2: Extract Dependency Signals
For each issue, parse 6 signal types:
2a. SQL Table Creation
Extract every CREATE TABLE <name> statement. Record which issue creates which table.
Issue #73 creates: notification_events, notification_channels, push_subscriptions,
notification_preferences, escalation_config
2b. SQL REFERENCES Clauses
Extract every REFERENCES <table>(id) clause. This is the primary dependency signal.
Issue #67: notification_queue_id REFERENCES notifications_queue(id)
→ #67 depends on whichever issue creates notifications_queue
→ That's #73 → dependency: #67 → #73
2c. SQL Table Usage in RPCs
Extract tables referenced in SELECT/INSERT/UPDATE/DELETE within RPC bodies.
Issue #68 RPC body: SELECT * FROM push_subscriptions WHERE ...
→ push_subscriptions created by #73 → dependency: #68 → #73
2d. TypeScript Import References
Extract hooks, components, and utilities referenced but not created by the issue.
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.
- 2d ago First seen · 180 lines · 0 tokens per session scan A 6fb0a2d22f14
dependency-mapper is an agent published in the GitHub repository Hulupeep/Specflow (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,526 tokens. 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 agents, from other repositories
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.
evolve-memo
Lightweight PASS-cycle memo agent (v8.57.0+, Layer P). Fires on PASS verdicts after ship to capture observations Scout/Triage saw but did NOT commit to topn. Single-pass, $0.10–0.20 per cycle. Emits carryover-todos.json and memo.md — does NOT do retrospective/digest work (that's the FAIL/WARN retrospective agent's…
pm
You are the Project Manager for AgentGuard. You coordinate all agents, manage the project board, and keep the project moving.
security-reviewer
Security-focused reviewer specializing in vulnerability assessment, supply chain security, and secure coding practices. Use PROACTIVELY when the user asks to "review security", "audit dependencies", "check for vulnerabilities", "security scan", or needs security-specific compliance assessment.
triage-labels
Les skills parlent en termes de cinq rôles canoniques de triage. Cette table mappe ces rôles vers les labels réels du tracker.
scrum-master
Principal Agile Orchestrator. Manages the virtual room, aggregates progress, resolves blockers, and reports to the user. Does not write code.