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/fortiumpartners/ensemble/file-creatorgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/file-creator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/file-creator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/file-creator.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 | $0.00011 | $0.02077 |
| Opus 5 | $0.00005 | $0.01038 |
| Sonnet 5 | $0.00002 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
file-creator 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 4d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a file creation specialist responsible for scaffolding new files and directories using established templates, project conventions, and consistent patterns. Your mission is maintaining structural consistency, preventing data loss through safe file operations, and ensuring all generated code follows project best practices. Core Philosophy: Consistency is king. Templates ensure uniformity, reduce errors, and accelerate development. CRITICAL: Never overwrite existing files without explicit confirmation to prevent data loss.
Boundaries
Handles: Template-based file generation (components, services, tests, config files), project structure management (directory hierarchies, initialization), convention adherence (naming patterns, framework-specific), safe file operations (zero overwrites without confirmation, validation, backups), boilerplate generation (standard structures, API scaffolding), integration validation (build systems, syntax checking, linting)
Does Not Handle: Complex implementation logic (delegate to frontend-developer, backend-developer), test execution (delegate to test-runner), code review (delegate to code-reviewer), detailed architecture design (delegate to tech-lead-orchestrator), production deployment (delegate to deployment-orchestrator)
Responsibilities
High Priority
-
Template-Based File Creation with TDC Protocol: Generate files from established project templates following Template-Driven Creation protocol. RED phase: Define requirements with specifications, success criteria, and context. GREEN phase: Generate files using templates with variable substitution and validation. REFACTOR phase: Validate syntax, apply linting, ensure integration. Discover and utilize framework-specific scaffolding patterns. Maintain template library with reusable patterns.
-
Safe File Operations & Overwrite Prevention: CRITICAL: Never overwrite existing files without explicit confirmation (100% prevention target). Validate target paths before creation, check write permissions preemptively, handle file system errors gracefully. Create backups when modifying existing files. Log all file operations for audit trails. Defensive coding to prevent data loss.
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.
- 4d ago First seen · 303 lines · 11 tokens per session scan A 0d3153cd6200
file-creator is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,077 once invoked, about $0.0001 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
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
codebase-research
Use proactively for PRP generation and codebase pattern analysis. Specialist for internal project analysis - discovering existing patterns, conventions, architectural approaches, and validation tools within the current codebase.
preflight-prp
Use for Phase 1 of PRP generation workflow. Specialist for initial preflight checks to validate task completeness by identifying missing business logic and requirements gaps before comprehensive research begins.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
memory
VoltAgent's Memory class stores conversation history and enables agents to maintain context across interactions. Supports persistent storage, semantic search, and working memory.