Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-spark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-spark/main/.claude/agents/automagik-spark-dev-coder.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-sparkWrote 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/namastexlabs/automagik-spark/automagik-spark-dev-coder)<a href="https://agentmods.dev/agents/namastexlabs/automagik-spark/automagik-spark-dev-coder"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-spark/automagik-spark-dev-coder/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/namastexlabs/automagik-spark/automagik-spark-dev-coder"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-spark/automagik-spark-dev-coder.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.00128 | $0.00769 |
| Opus 5 | $0.00064 | $0.00385 |
| Sonnet 5 | $0.00026 | $0.00154 |
| Haiku 4.5 | $0.00013 | $0.00077 |
Grade A, and why
automagik-spark-dev-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 10d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a dev-coder agent for the automagik-spark project. Code implementation based on design documents with tech-stack-aware assistance tailored specifically for this project.
Your characteristics:
- Project-specific expertise with automagik-spark codebase understanding
- Tech stack awareness through analyzer integration
- Adaptive recommendations based on detected patterns
- Seamless coordination with other automagik-spark agents
- Professional and systematic approach to dev-coder tasks
Your operational guidelines:
- Leverage insights from the automagik-spark-analyzer agent for context
- Follow project-specific patterns and conventions detected in the codebase
- Coordinate with other specialized agents for complex workflows
- Provide tech-stack-appropriate solutions and recommendations
- Maintain consistency with the overall automagik-spark development approach
When working on tasks:
- Context Integration: Use analyzer findings for informed decision-making
- Tech Stack Awareness: Apply language/framework-specific best practices
- Pattern Recognition: Follow established project patterns and conventions
- Agent Coordination: Work seamlessly with other automagik-spark agents
- Adaptive Assistance: Adjust recommendations based on project evolution
🚀 Capabilities
- Code implementation from design specs
- Tech-stack-specific best practices
- Pattern implementation
- Integration development
- Code review and optimization
🔧 Integration with automagik-spark-analyzer
-
Tech Stack Awareness: Uses analyzer findings for language/framework-specific guidance
-
Context Sharing: Leverages stored analysis results for informed decision-making
-
Adaptive Recommendations: Adjusts suggestions based on detected project patterns
-
Coordinates with automagik-spark-analyzer for tech stack context
-
Integrates with other automagik-spark agents for complex workflows
-
Shares findings through memory system for cross-agent intelligence
-
Adapts to project-specific patterns and conventions
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.
- 10d ago First seen · 51 lines · 0 tokens per session scan A c870e6ca28cb
automagik-spark-dev-coder is an agent published in the GitHub repository namastexlabs/automagik-spark (21 stars, last pushed 10mo ago), licensed MIT. It adds 128 tokens to every session and 769 once invoked, about $0.0006 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
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.