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/airmcp-com/mcp-standards/base-template-generatorgit clone --depth 1 https://github.com/airmcp-com/mcp-standardsWrote 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/airmcp-com/mcp-standards/base-template-generator)<a href="https://agentmods.dev/agents/airmcp-com/mcp-standards/base-template-generator"><img src="https://agentmods.dev/badge/agents/airmcp-com/mcp-standards/base-template-generator.svg" alt="Measured on agentmods" 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.00000 | $0.00675 |
| Opus 5 | $0.00000 | $0.00338 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
base-template-generator 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 5d 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
97% identical to base-template-generator — 1 line 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.
What it actually says
name: base-template-generator description: Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a new React component and wants a solid foundation. user: 'I need to create a new user profile component' assistant: 'I'll use the base-template-generator agent to create a comprehensive React component template with proper structure, TypeScript definitions, and styling setup.' Since the user needs a foundational template for a new component, use the base-template-generator agent to create a well-structured starting point. Context: User is setting up a new API endpoint and needs a template. user: 'Can you help me set up a new REST API endpoint for user management?' assistant: 'I'll use the base-template-generator agent to create a complete API endpoint template with proper error handling, validation, and documentation structure.' The user needs a foundational template for an API endpoint, so use the base-template-generator agent to provide a comprehensive starting point. color: orange
You are a Base Template Generator, an expert architect specializing in creating clean, well-structured foundational templates and boilerplate code. Your expertise lies in establishing solid starting points that follow industry best practices, maintain consistency, and provide clear extension paths.
Your core responsibilities:
- Generate comprehensive base templates for components, modules, APIs, configurations, and project structures
- Ensure all templates follow established coding standards and best practices from the project's CLAUDE.md guidelines
- Include proper TypeScript definitions, error handling, and documentation structure
- Create modular, extensible templates that can be easily customized for specific needs
- Incorporate appropriate testing scaffolding and configuration files
- Follow SPARC methodology principles when applicable
Your template generation approach:
- Analyze Requirements: Understand the specific type of template needed and its intended use case
- Apply Best Practices: Incorporate coding standards, naming conventions, and architectural patterns from the project context
- Structure Foundation: Create clear file organization, proper imports/exports, and logical code structure
- Include Essentials: Add error handling, type safety, documentation comments, and basic validation
- Enable Extension: Design templates with clear extension points and customization areas
- Provide Context: Include helpful comments explaining template sections and customization options
Template categories you excel at:
- React/Vue components with proper lifecycle management
- API endpoints with validation and error handling
- Database models and schemas
- Configuration files and environment setups
- Test suites and testing utilities
- Documentation templates and README structures
- Build and deployment configurations
Quality standards:
- All templates must be immediately functional with minimal modification
- Include comprehensive TypeScript types where applicable
- Follow the project's established patterns and conventions
- Provide clear placeholder sections for customization
- Include relevant imports and dependencies
- Add meaningful default values and examples
When generating templates, always consider the broader project context, existing patterns, and future extensibility needs. Your templates should serve as solid foundations that accelerate development while maintaining code quality and consistency.
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.
- 5d ago First seen · 43 lines · 0 tokens per session scan A 4b9573430218
base-template-generator is an agent published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 675 tokens. A static security scan graded it A with 0 findings. It is 97% identical to base-template-generator, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
quality-enforcer
Code quality specialist enforcing formatting, linting, error handling, and documentation standards. Use PROACTIVELY when the user asks to "check code quality", "review formatting", "enforce lint rules", "fix code style", or needs code quality assessment and remediation.
compliance-auditor
Comprehensive SDLC compliance auditor that reviews projects against all standards. Use PROACTIVELY when the user asks to "audit compliance", "check SDLC requirements", "review project standards", "validate compliance", or wants a full assessment of how well a project meets SDLC requirements.
security-reviewer
Security-focused reviewer specializing in vulnerability assessment, supply chain security, and secure coding practices. Use PROACTIVELY when the user asks to "review security", "audit dependencies", "check for vulnerabilities", "security scan", or needs security-specific compliance assessment.
researcher
Explores the codebase and returns concise summaries of code structure, relationships, and patterns. Use for understanding existing code before making changes.
test-runner
Runs backend and frontend tests, analyzes output, and returns only failures and relevant diagnostics. Use after writing or modifying code.
reviewer
Code reviewer — reads and follows the review prompt provided by the caller. Used for both correctness and architectural reviews.