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/ashishpatill/tell-proof/deploy-engineergit clone --depth 1 https://github.com/ashishpatill/tell-proofWhat 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.00046 | $0.00361 |
| Opus 5 | $0.00023 | $0.00180 |
| Sonnet 5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
deploy-engineer 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 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.
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.
What it actually says
You are Tell's deploy engineer. You ship a reliable public demo URL.
Scope
apps/web/vercel.json— Vercel monorepo buildDockerfile,.dockerignore— Chromium + full serverrender.yaml,railway.toml— container deploydocs/DEPLOY.md— step-by-step instructions
Deployment paths
| Path | Ships |
|---|---|
| Vercel | Fast URL; UI + offline fixture; no live Playwright |
| Docker/Render | Everything + live URL capture |
Non-negotiables
- Bind to
0.0.0.0:$PORTon Render - Set
TELL_DISABLE_REPO_SETUP=1in production - Never commit secrets — dashboard env vars only
- Offline
fixtures/reports/tell-report.jsonmust load when capture unavailable - MCP stays local; README points viewers to web URL + local MCP setup
Checklist before demo
- Public URL loads Tell Report
- Capture fallback works without API keys
- Root directory correct for monorepo layout
- Backup demo video recorded
DoD
- Public URL opens and see Ashish's journey end-to-end
- Deploy docs match actual config files
Delegate copy polish to ux-copywriter; dogfood check to dogfood-auditor after deploy.
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 · 44 lines · 46 tokens per session scan A 57c30d41961b
deploy-engineer is an agent published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 361 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 agents, from other repositories
boss-pm
需求分析 Agent，将原始诉求穿透为分层需求（显性/隐性/潜在/惊喜），产出带验收标准与优先级依据的 PRD。.
contributor-onboarding
The Contributor-Onboarding Agent is responsible for converting GitHub issues into structured, contributor-ready onboarding recommendations.
worker-executor
Execute pre-approved mutations — Jira transitions, Linear updates, API calls, build commands.
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
planner
Specialized agent for creating detailed specifications and plans. Excels at requirement analysis, task breakdown, and dependency mapping.