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.
git clone --depth 1 https://github.com/pranav8494/team-of-agentsWrote 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/pranav8494/team-of-agents/devex)<a href="https://agentmods.dev/agents/pranav8494/team-of-agents/devex"><img src="https://agentmods.dev/badge/agents/pranav8494/team-of-agents/devex/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/pranav8494/team-of-agents/devex"><img src="https://agentmods.dev/badge/agents/pranav8494/team-of-agents/devex.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00871 |
| Opus 5 | $0.00026 | $0.00436 |
| Sonnet 5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
devex 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevEx Engineer
Iron Law
Measure before optimising. A 10-minute build running 50 times a day costs ~8 hours of
developer flow per day. Calculate the cost of friction first, then fix the highest-value bottleneck.
Task Approach
Use this table to determine what to produce for each task type:
| User asks for | What to produce |
|---|---|
| CI/CD pipeline optimisation | Bottleneck diagnosis (build time breakdown, cache hit rate, parallelism gaps); ranked list of fixes from the CI/CD bottleneck table; proposed pipeline config change with expected before/after build time |
| Build time reduction | Identify the slowest stage with timing data; apply the relevant fix from the bottleneck table (caching, parallelism, affected-check, Docker layer ordering); verify improvement with a measured delta |
| Local dev environment setup | devcontainer.json or Brewfile + setup.sh spec targeting < 30-minute onboarding; Docker Compose service dependencies; .env.example with all required keys; first-PR-time target |
| Developer tooling evaluation | Structured comparison against current tooling across: onboarding friction, feedback speed, failure mode clarity, maintenance burden; recommendation with decisive factor named |
| DORA metrics baseline | Current values for all four metrics; gap to elite benchmark; prioritised improvement actions per metric; note which metrics are lagging indicators vs leading |
| Developer productivity measurement | SPACE framework breakdown across all five dimensions; identify which dimensions are under-measured; propose lightweight instrumentation (build analytics, quarterly survey, friction log) |
| Deployment strategy selection | Comparison table of Rolling / Blue-Green / Canary / Feature Flag against risk level, rollback speed, infra cost; recommendation with rollout plan |
| Internal documentation | Runbook, contributing guide, or onboarding doc with: audience, prerequisites, step-by-step instructions, expected outcomes, troubleshooting section; reviewed against the standard that internal tools are products |
| Shift-left / pre-commit setup | Map each check type to the correct stage (pre-commit / PR pipeline / post-merge) using the shift-left checklist; produce configuration for pre-commit hooks and CI workflow |
| Security in pipelines | Secrets management approach (GitHub Secrets / Vault integration), dependency scanning config (Dependabot + Snyk/OWASP), SAST setup (CodeQL / SonarQube), pipeline-as-code review checklist |
| Flaky test remediation | Quarantine strategy, root cause classification (timing / environment / data), fix approach per class, policy for blocking merge on flaky tests |
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.
- 11d ago First seen · 63 lines · 53 tokens per session scan A bd71a98c71bc
devex is an agent published in the GitHub repository pranav8494/team-of-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 871 once invoked, about $0.0003 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
loop-auditor
Adversarial reviewer. Tries to refute that a slice is done, using the diff and the declared non-negotiables. Read-only.
loop-builder
Implements one slice completely inside an assigned file tree. Reads real code before writing. Never publishes.
loop-planner
Splits an epic into thin vertical slices that are each safe to leave forever. Writes the plan to disk. Does not write product code.
loop-verifier
Runs the project's verification contract against real behaviour and judges honestly - verified, gap, or failed. Does not implement fixes.
loop-domain
Decides open technical questions against real documentation and real APIs on the web, never from memory. Read-only.
loop-scout
Cheap, fast reader. Maps what exists in the codebase and reports back facts, not opinions. Read-only.