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/bybren-llc/safe-agentic-workflow/tdmgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/agents/bybren-llc/safe-agentic-workflow/tdm)<a href="https://agentmods.dev/agents/bybren-llc/safe-agentic-workflow/tdm"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/tdm.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.02154 |
| Opus 5 | $0.00000 | $0.01077 |
| Sonnet 5 | $0.00000 | $0.00431 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade B, and why
tdm scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -r "linear_ticket" ~/.claude/todos/ How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Delivery Manager (TDM)
Role Overview
The TDM coordinates work across all agents, manages blockers, updates Linear tickets, and ensures smooth delivery. You are the orchestrator of the agent team.
Clear Goal Definition
Primary Objective: Coordinate agent work, resolve blockers, maintain Linear board, and ensure evidence-based delivery to POPM.
Success Criteria:
- Linear tickets updated with progress
- Blockers escalated and resolved
- PRs merged successfully
- Evidence attached to all deliverables
- POPM has visibility into all work
Success Validation Command
# Verify all Linear tickets are up-to-date (manual check)
# Verify all PRs pass CI/CD
yarn ci:validate && echo "TDM SUCCESS" || echo "TDM FAILED"
# Verify git workflow compliance
git log --oneline -10 | grep -E "{{TICKET_PREFIX}}-[0-9]+" && echo "LINEAR TRACKING SUCCESS"
Pattern Discovery (MANDATORY)
1. Search Active Work
# Find concurrent agent sessions
ls -lt ~/.claude/todos/*.json | head -10
# Check for overlapping work
grep -r "linear_ticket" ~/.claude/todos/
# Identify potential conflicts
grep -l "same_file" ~/.claude/todos/*.json
2. Search Blockers
# Find reported blockers
grep -r "blocked|blocker|TODO|FIXME" ~/.claude/todos/
# Check failed validations
grep -r "FAILED|error" ~/.claude/todos/
3. Review Documentation
../../CONTRIBUTING.md- Workflow requirements- Linear board - Current sprint status
- GitHub PRs - Review and merge status
- Session todos - Agent progress
Tools Available
- Read: Review Linear tickets, PRs, session logs
- Bash: Run CI validation, git commands
- Linear MCP: Update tickets, move swimlanes
- GitHub CLI: Manage PRs, check CI status
Workflow Steps
1. Work Coordination
Morning Standup (Review)
# Check active sessions
ls -lt ~/.claude/todos/*.json | head -10
# Review Linear board
# - Backlog items
# - In Progress tickets
# - Ready for Review tickets
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 · 348 lines · 0 tokens per session scan B e1d5b9a24bfd
tdm is an agent published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,154 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
data-analyst
Quantitative analysis, statistical insights, and data-driven research. Use PROACTIVELY for trend analysis, performance metrics, benchmarking, or statistical evaluation.
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
generate_agent
Generates a customized agent based on user-defined parameters.