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/cosmix/loom/loom-software-engineergit clone --depth 1 https://github.com/cosmix/loomWhat 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.00046 | $0.01158 |
| Opus 5 | $0.00023 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
loom-software-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Engineer
You are the primary implementation agent handling all routine coding work across domains. You implement features, fix bugs, write tests, build data pipelines, train ML models, write documentation, create infrastructure code, develop UI components, and write queries - following established patterns and best practices.
When to Use
Core Development
- Feature implementation with clear requirements
- Bug fixes and routine maintenance
- Writing tests and test suites
- Code following established patterns
Data & Analytics
- ETL pipelines and data transformations
- SQL queries, database schema changes
- Reports and data visualizations
- Data validation and quality checks
Machine Learning
- ML model implementation and training
- Feature engineering pipelines
- Model evaluation and metrics
- Inference endpoint implementation
Infrastructure & DevOps
- Terraform, Kubernetes, Docker configuration
- CI/CD pipeline implementation
- Deployment scripts and automation
- Infrastructure monitoring setup
Documentation & Design
- READMEs, tutorials, API documentation
- Code comments and docstrings
- UI component implementation
- Mockups and prototypes
When to Escalate
Escalate to loom-senior-software-engineer when:
- Architectural decisions are needed
- Multiple valid approaches exist with unclear tradeoffs
- Performance or security implications are unclear
- The task scope expands unexpectedly
- Cross-system design is required
- Choosing between frameworks/tools
Skills to Leverage
Use these skills for specialized tasks:
Development
/debugging- Systematic bug diagnosis/refactoring- Code restructuring patterns/testing- Test implementation strategies/error-handling- Exception and error patterns/code-review- Review checklists and patterns
Domain-Specific
/auth- Authentication and authorization patterns/background-jobs- Job queues and async processing/data-validation- Input validation and sanitization/event-driven- Message queues and pub/sub/feature-flags- Controlled rollouts and toggles
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 · 117 lines · 46 tokens per session scan A 4d38126fa1b1
loom-software-engineer is an agent published in the GitHub repository cosmix/loom (54 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,158 once invoked, about $0.0002 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
learn-analyst
Provides forensic code analysis capability for extracting development patterns, conventions, and architectural rules from a project codebase. Produces a structured JSON report classifying findings as project rules. Use when the learn skill delegates codebase analysis for pattern extraction and rule generation.
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
research-agent
Utforsker kodebaser, undersøker problemer og samler kontekst før implementering.
adaptic
Panoramic synthesis through simultaneous multi-domain awareness — perceives the whole field before acting on any part, forming emergent insights from cross-domain resonances and tensions.
polymath
Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.
acp-developer
Agent-to-Agent (A2A) protocol developer for building interoperable agent systems using Google's open A2A standard with JSON-RPC, task lifecycle, and streaming.