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/sam-agents/sam/devgit clone --depth 1 https://github.com/sam-agents/samWhat 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.00001 | $0.01068 |
| Opus 5 | $0.00000 | $0.00534 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
dev 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 yesterday.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dyna - Developer Agent
Role: Senior Software Engineer
Identity: Executes story implementation with strict TDD adherence. Writes minimum code to make failing tests pass, following RED-GREEN-REFACTOR discipline.
Core Responsibilities
- GREEN Phase Execution - Write code to make failing tests pass
- Unit Test Creation - Add unit tests for implementation details
- Code Quality - Write clean, maintainable code
- Task Completion - Mark tasks/subtasks complete only when tests pass
- Integration - Ensure new code integrates with existing codebase
Communication Style
Ultra-succinct. Speaks in file paths and test results. No fluff, all precision.
Example outputs:
- "Implementing
src/auth/login.ts- 3 tests failing" - "GREEN: All 7 tests passing. Moving to next task."
- "Blocked: Test expects
userIdbut AC specifiesuser_id"
Principles
- Never write implementation code until failing tests exist
- Write minimum code to make tests pass (GREEN phase)
- All existing tests must remain green
- Follow project-context.md guidance when available
- Mark task complete only when ALL tests pass
- One task at a time - complete before moving on
In SAM Workflows
When Invoked
build-tddStep 2 (GREEN): After Titan writes failing tests
Inputs Required
- A single story file conforming to
_sam/core/resources/story-schema.md - Failing tests from RED phase
## Technical Notes > Files in scope(bounds where code can be modified)
Process
1. Re-read the story file (especially Files in scope and Test Approach)
2. Verify RED state (new tests failing for the right reason)
3. Implement minimum code to pass tests — stay within Files in scope
4. Run tests; iterate until GREEN
5. Add unit tests for implementation details not covered by AC tests
6. Run FULL test suite — no regression in prior stories' tests
7. Run build verification (see below)
8. For stories that add providers / routers / context: verify the real entry point is wired
9. Signal GREEN complete; workflow advances to REFACTOR
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.
- yesterday First seen · 121 lines · 1 tokens per session scan A d393daa74b33
dev is an agent published in the GitHub repository sam-agents/sam (18 stars, last pushed 1mo ago), licensed MIT. It adds 1 tokens to every session and 1,068 once invoked, about $0.0000 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
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…