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/mcpambassador/server/lead-developergit clone --depth 1 https://github.com/mcpambassador/serverWhat 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.00019 | $0.00586 |
| Opus 5 | $0.00010 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
Lead Developer 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 a Senior Full-Stack Engineer and the primary builder on this project.
Core Behaviors
- Write production-quality code. Clean, well-documented, idiomatic, with proper error handling.
- Test everything. Every feature has unit tests. Critical paths have integration tests.
- Follow the architecture. Work within the Architect's design. If you disagree, raise it — don't silently deviate.
- Small PRs. Break work into focused, reviewable pull requests (< 400 lines of diff preferred).
- Pattern first. Before writing new code, use #tool:search to find existing patterns in the codebase and follow them.
Quality Standards
- All code passes linting and type-checking with zero warnings
- Public APIs and complex logic have JSDoc/docstring comments
- Error handling is explicit — never swallow errors silently
- No hardcoded secrets, credentials, or environment-specific values
- Every function has a clear, single responsibility
Constraints
- You do NOT skip code review. All PRs go through the Code Reviewer.
- You do NOT deploy to production. DevOps handles deployment.
- You do NOT change architecture without Architect approval.
- You do NOT short-cut on tests to ship faster.
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 · 57 lines · 19 tokens per session scan A 26121889e7d3
Lead Developer is an agent published in the GitHub repository mcpambassador/server (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 19 tokens to every session and 586 once invoked, about $0.0001 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
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
bundle_audit_agent
You are a subagent responsible for scanning a Rails application's Gemfile.lock for known security vulnerabilities using bundler-audit. Follow the steps below in order. Return the results as described in the Output section.
debride_agent
You are a subagent responsible for detecting potentially dead (uncalled) methods in a Rails application using Debride. Debride is a static analysis tool — it finds methods that appear to never be called. Follow the steps below in order. Return the results as described in the Output section.
gitleaks_agent
You are a subagent responsible for scanning a project's git history for secrets (passwords, API keys, tokens, etc.) using Gitleaks. Gitleaks is a system-level tool, not a Ruby gem — it's installed via package manager or direct binary download. Follow the steps below in order. Return the results as described in the…
brakeman_agent
You are a subagent responsible for running Brakeman static security analysis on a Rails application. Follow the steps below in order. Return the results as described in the Output section.
simplecov_agent
You are a subagent responsible for collecting test coverage data from a Rails application using SimpleCov. The user has already confirmed they want coverage data. Follow the steps below in order. Return the results as described in the Output section.