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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/autonomous-developer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/autonomous-developer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/autonomous-developer/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/technickai/ai-coding-config/autonomous-developer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/autonomous-developer.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.00028 | $0.01305 |
| Opus 5.5 | $0.00011 | $0.00522 |
| Sonnet 5.5 | $0.00006 | $0.00261 |
| Haiku 4.5 | $0.00003 | $0.00130 |
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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 1mo ago First seen · 139 lines · 28 tokens per session scan A a3bb20e715d2
autonomous-developer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 1,305 once invoked, about $0.0001 per session on Opus 5.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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.