Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/agents/tdm.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/rendertrust/tdm)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/tdm"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/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.1 | $0.00017 | $0.02103 |
| Opus 5 | $0.00009 | $0.01052 |
| Sonnet 5 | $0.00003 | $0.00421 |
| Haiku 4.5 | $0.00002 | $0.00210 |
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 yesterday.
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/ This is a copy
94% identical to tdm — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 "REN-[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.
- yesterday First seen · 348 lines · 17 tokens per session scan B 28a8d44374d2
tdm is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,103 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 94% identical to tdm, differing in 26 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…