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 commands/keychain-io/trustable-ai/dependency-managementgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/commands/keychain-io/trustable-ai/dependency-management)<a href="https://agentmods.dev/commands/keychain-io/trustable-ai/dependency-management"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/dependency-management.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.00000 | $0.02060 |
| Opus 5 | $0.00000 | $0.01030 |
| Sonnet 5 | $0.00000 | $0.00412 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
dependency-management 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 4d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Management Workflow
Project: trusted-ai-development-workbench Workflow: Dependency Management Purpose: Monitor, update, and secure project dependencies
Output Formatting Requirements
IMPORTANT: Use actual Unicode emojis in reports, NOT GitHub-style shortcodes.
Workflow Overview
┌─────────────────────────────────────────────────────────────────────────────┐
│ DEPENDENCY MANAGEMENT │
│ │
│ Step 1: Scan current dependencies │
│ Step 2: Categorize by priority │
│ Step 3: /senior-engineer → Impact analysis (if outdated) │
│ Step 4: /security-specialist → Vulnerability assessment (if vulns) │
│ Step 5: Generate update plan │
│ Step 6: Create work items │
│ Step 7: Generate health report │
│ │
│ Each agent command spawns a FRESH CONTEXT WINDOW via Task tool │
└─────────────────────────────────────────────────────────────────────────────┘
Step 1: Scan Current Dependencies
Python Project:
# List current dependencies
pip list --format=json > .claude/temp/current-deps.json
# Check for outdated packages
pip list --outdated --format=json > .claude/temp/outdated-deps.json
# Security audit (requires pip-audit)
pip-audit --format=json > .claude/temp/security-audit.json 2>&1 || true
Step 2: Categorize Dependencies
# Parse scan results
import json
from pathlib import Path
# Load results
outdated = json.loads(Path(".claude/temp/outdated-deps.json").read_text())
security = json.loads(Path(".claude/temp/security-audit.json").read_text())
# Categorize
critical_security = [] # CVE Critical
high_priority = [] # CVE High or EOL
medium_priority = [] # Minor updates
low_priority = [] # Patch updates
for vuln in security.get('vulnerabilities', []):
severity = vuln.get('severity', 'unknown')
if severity == 'critical':
critical_security.append(vuln)
elif severity == 'high':
high_priority.append(vuln)
else:
medium_priority.append(vuln)
print(f"📦 Dependency Scan Results:")
print(f" 🔴 Critical: {len(critical_security)}")
print(f" 🟠 High: {len(high_priority)}")
print(f" 🟡 Medium: {len(medium_priority)}")
print(f" 🟢 Low: {len(low_priority)}")
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.
- 4d ago First seen · 373 lines · 0 tokens per session scan A dfaf287f03ed
dependency-management is a command published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,060 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.