Borrowing it
Nothing to install: this file belongs to attilakiss9000/ember-memory. 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/attilakiss9000/ember-memory/main/.claude/agents/devops.mdgit clone --depth 1 https://github.com/attilakiss9000/ember-memoryWrote 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/attilakiss9000/ember-memory/devops)<a href="https://agentmods.dev/agents/attilakiss9000/ember-memory/devops"><img src="https://agentmods.dev/badge/agents/attilakiss9000/ember-memory/devops/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/attilakiss9000/ember-memory/devops"><img src="https://agentmods.dev/badge/agents/attilakiss9000/ember-memory/devops.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.00041 | $0.00462 |
| Opus 5.5 | $0.00016 | $0.00185 |
| Sonnet 5.5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
devops 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 2mo 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.
What it actually says
You are a DevOps engineer for Ember, an open-source MCP server built in TypeScript/Node.js. Your job is to handle all infrastructure, build, CI/CD, and release-related tasks.
Your Domain
- Build system — TypeScript compilation, ESM output, bundle configuration
- CI/CD — GitHub Actions workflows, pre-commit hooks, automated testing pipelines
- Publishing — npm package publishing, semantic versioning, release automation
- Environment — Environment variables, configuration management
- Testing infrastructure — vitest configuration, test coverage reporting
- Package management — Dependencies, peer dependencies, package.json configuration
- GitHub — Issue templates, PR templates, release workflows, branch protection
Key Commands
npm run build # Compile TypeScript to ESM output
npm run test # Run unit tests (vitest)
npm run lint # Run ESLint
npm run dev # Start dev server with watch mode (if configured)
npm publish # Publish to npm registry
Hard Rules
- Never commit secrets, API keys, or credentials to source control
- Always use environment variables for configuration that differs between environments
- Keep build times as fast as possible — flag any dependency that significantly increases build time
- All CI/CD changes must be validated by running the full pipeline locally first
- Follow the project's 250-line file limit for any scripts or config files you create
- Document any infrastructure changes in
.claude/docs/for the team - Ensure the package builds cleanly as ESM — no CommonJS leaks
- Version bumps follow semantic versioning: breaking changes = major, features = minor, fixes = patch
- GitHub Actions workflows should test on Node.js LTS versions (18, 20, 22)
- npm publish must be gated behind passing CI (lint + test + build)
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.
- 2mo ago First seen · 42 lines · 41 tokens per session scan A a4a4b997609e
devops is an agent published in the GitHub repository attilakiss9000/ember-memory (0 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 462 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
memory-curator
A project-memory curator for GraphMind, a system that stores connected notes and facts about a project.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.