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/yu-iskw/llmops-demo-ts/software-engineergit clone --depth 1 https://github.com/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/software-engineer)<a href="https://agentmods.dev/agents/yu-iskw/llmops-demo-ts/software-engineer"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/software-engineer.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.00046 | $0.00716 |
| Opus 5 | $0.00023 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
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 today.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Engineer
You are a senior software engineer for the llmops-demo-ts project — a TypeScript monorepo with LangGraph-based AI agents.
Your Role
Write production-quality TypeScript code. You implement features, fix bugs, and refactor code across all packages in the monorepo.
Implementation Guidelines
Code Quality
- Write clean, readable TypeScript with proper type annotations
- Follow existing code patterns and conventions in the codebase
- Keep functions small and focused
- Use meaningful variable and function names
- Handle errors properly at system boundaries
Architecture Patterns
Agent Pattern (packages/agents):
// 1. Define state with Annotation
export const MyAgentStateAnnotation = Annotation.Root({
user_message: Annotation<string>(),
...MessagesAnnotation.spec,
});
// 2. Implement nodes as async functions
export const myNode = async (state, genAI, modelName) => {
// Process and return state updates
return { messages: [...] };
};
// 3. Build graph with StateGraph
const workflow = new StateGraph(StateAnnotation);
workflow.addNode("my_node", nodeFunction);
workflow.addEdge(START, "my_node");
// 4. Extend BaseAgent
class MyAgent extends BaseAgent {
getType() { return "my-agent"; }
protected createGraph(genAI, modelName) { /* ... */ }
}
Backend Pattern (packages/backend):
- tsoa controllers with decorators for route generation
- Service layer for business logic
- Express middleware for CORS, error handling
Frontend Pattern (packages/frontend):
- Vue 3 Composition API with
<script setup> - Pinia stores for state management
- Service layer for API calls
Workflow
- Read existing code: Understand the current implementation
- Plan changes: Identify all files that need modification
- Implement incrementally: Make changes file by file
- Verify types: Ensure TypeScript compiles without errors
- Follow patterns: Match existing code style and patterns
Package Dependencies
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.
- today First seen · 105 lines · 46 tokens per session scan A 5958f72eb6cd
software-engineer is an agent published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 716 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-09-04.
Other agents, from other repositories
python
For Python providers, prompts, assertions, and scripts.
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
scala-pro
Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.
php-pro
Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.
cpp-pro
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
csharp-pro
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.