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/summarybotng/summarybot-ng/base-template-generatorgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWhat 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.00249 | $0.00677 |
| Opus 5 | $0.00125 | $0.00338 |
| Sonnet 5 | $0.00050 | $0.00135 |
| Haiku 4.5 | $0.00025 | $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 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 base-template-generator — 84 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.
What it actually says
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.
- 2d ago First seen · 43 lines · 0 tokens per session scan A f6db0aecf24a
base-template-generator is an agent published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 2mo ago), licensed MIT. It adds 249 tokens to every session and 677 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to base-template-generator, differing in 84 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.