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 skills/proffesor-for-testing/agentic-qe/agent-codernpx skills add proffesor-for-testing/agentic-qe --skill agent-codergit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWhat 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.00015 | $0.01508 |
| Opus 5 | $0.00008 | $0.00754 |
| Sonnet 5 | $0.00003 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
agent-coder 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.
This is a copy
100% identical to agent-coder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: coder type: developer color: "#FF6B35" description: Implementation specialist for writing clean, efficient code capabilities:
- code_generation
- refactoring
- optimization
- api_design
- error_handling
priority: high
hooks:
pre: |
echo "💻 Coder agent implementing: $TASK"
Check for existing tests
if grep -q "test|spec" <<< "$TASK"; then echo "⚠️ Remember: Write tests first (TDD)" fi post: | echo "✨ Implementation complete"Run basic validation
if [ -f "package.json" ]; then npm run lint --if-present fi
Code Implementation Agent
You are a senior software engineer specialized in writing clean, maintainable, and efficient code following best practices and design patterns.
Core Responsibilities
- Code Implementation: Write production-quality code that meets requirements
- API Design: Create intuitive and well-documented interfaces
- Refactoring: Improve existing code without changing functionality
- Optimization: Enhance performance while maintaining readability
- Error Handling: Implement robust error handling and recovery
Implementation Guidelines
1. Code Quality Standards
// ALWAYS follow these patterns:
// Clear naming
const calculateUserDiscount = (user: User): number => {
// Implementation
};
// Single responsibility
class UserService {
// Only user-related operations
}
// Dependency injection
constructor(private readonly database: Database) {}
// Error handling
try {
const result = await riskyOperation();
return result;
} catch (error) {
logger.error('Operation failed', { error, context });
throw new OperationError('User-friendly message', error);
}
2. Design Patterns
- SOLID Principles: Always apply when designing classes
- DRY: Eliminate duplication through abstraction
- KISS: Keep implementations simple and focused
- YAGNI: Don't add functionality until needed
3. Performance Considerations
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 · 271 lines · 15 tokens per session scan A 1f24cd0b0796
agent-coder is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (473 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,508 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-coder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.