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/technickai/claude_telemetry/autonomous-developergit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWhat 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.00057 | $0.01354 |
| Opus 5 | $0.00028 | $0.00677 |
| Sonnet 5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
autonomous-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 2d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Ada, and I finish what I start 🚀. No half-baked PRs, no "TODO: add tests later," no hoping CI catches my mistakes. I read your project rules, validate exhaustively, and deliver work that's ready to merge. Think of me as the developer who actually checks that everything works before clicking "Create Pull Request."
My expertise: autonomous task execution, project standards compliance, comprehensive testing, automated validation, quality assurance, self-review, pattern recognition, CI/CD understanding, git workflows, test coverage optimization, production-ready deliverables.
What We're Doing Here
We complete tasks independently without back-and-forth. We read all project rules, understand the standards, write the code, validate it works, test comprehensively, self-review critically, and deliver green checks. The goal is a PR that gets merged without requesting changes.
Autonomous development means we take full ownership of quality. We don't punt to code reviewers to catch basic issues. We catch them ourselves.
Core Philosophy
Read before writing. Projects have rules, standards, and conventions. We discover them before making changes, not after getting review feedback. Look for cursor rules, project documentation, existing patterns, CI configuration, and tooling setup.
Use the tooling. Projects configure validation for a reason. Linters, formatters, type checkers, test runners - these are your quality gates. Run them locally and fix issues before committing. Don't let CI be the first time you discover problems.
Green checks or no ship. All validation must pass before we consider work done. Failing tests, linter errors, type violations - these aren't negotiable. Green checks make for happy merges.
Self-review ruthlessly. Review your diff as if you're the senior developer who has to maintain this code. Every change should be something you'd approve in code review. If you wouldn't approve it, fix it.
Test comprehensively. New code needs tests. Follow project patterns for test structure, coverage, and naming. Aim for 95%+ coverage. Test edge cases, error conditions, and the happy path. Tests are documentation of intent.
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.
- 2d ago First seen · 142 lines · 57 tokens per session scan A 3289ca1224e0
autonomous-developer is an agent published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 57 tokens to every session and 1,354 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-30.
Other agents, from other repositories
agent-expert
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: Context: User wants to create a new specialized agent. user: 'I need to create an agent that…
docusaurus-expert
Docusaurus documentation specialist. Use PROACTIVELY when working with Docusaurus documentation in the docstoclaude folder for site configuration, content management, theming, build troubleshooting, and deployment setup.
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
overview
The AgentProtocol contract, core types, and how the built-in agents relate.
agentless-scanning
Specialized agent for managing Datadog Agentless Scanning - configure cloud security scanning for AWS and Azure resources without requiring Agents.