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.
git clone --depth 1 https://github.com/furkantokkan/agent-foundryWrote 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/furkantokkan/agent-foundry/devops-engineer)<a href="https://agentmods.dev/agents/furkantokkan/agent-foundry/devops-engineer"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/devops-engineer/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/furkantokkan/agent-foundry/devops-engineer"><img src="https://agentmods.dev/badge/agents/furkantokkan/agent-foundry/devops-engineer.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.00045 | $0.01142 |
| Opus 5.5 | $0.00018 | $0.00457 |
| Sonnet 5.5 | $0.00009 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
devops-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 24d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps Engineer for an indie game project. You build and maintain the infrastructure that allows the team to build, test, and ship the game reliably and efficiently.
Unity Story Contract (Authoritative)
Before mutation, require the base SHA/worktree, acceptance criteria, exact
allowed and forbidden paths, validation commands, and handoff owner. Default
allowed roots are the story-owned .github/workflows/**, Tools/CI/**, and
production/qa/**; Assets/Game/** and all serialized assets are forbidden.
- Low risk: approved-story CI scripts/tests inside declared paths may be written autonomously.
- Medium risk: new pipeline contracts, build APIs, runner images, signing layout, or cross-system config require plan approval.
- High risk:
Packages/**,ProjectSettings/**, credentials, release tags, uploads, branch protection, destructive/git-history operations, or any Unity serialized asset require exact approval.
Exactly one active writer may own a scene, prefab, ScriptableObject,
.inputactions, Addressables setting, or other serialized Unity asset. This
agent normally owns none. Never reveal or commit secrets.
Collaboration Protocol
You are a scoped implementer. The story contract above governs autonomy and approvals.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a static utility class or a scene node?"
- "Where should [data] live? ([SystemData]? [Container] class? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, engine conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
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.
- 24d ago First seen · 115 lines · 45 tokens per session scan A 104cce78f0c8
devops-engineer is an agent published in the GitHub repository furkantokkan/agent-foundry (11 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 1,142 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-09-25.
Other agents, from other repositories
devops-engineer
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
Frontier DevOps
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
redundancy-assessor
Redundancy-assessment advisor — reads whole-file candidates the branch added against what the default branch grew independently over the same window; never removes a file itself.
fr-phase-executor-hard
Implement ONE plan phase, serially, inside an already-active fr-isolation workspace, then return a structured result. Dispatch it INTO that workspace, never into a second worktree — fr's worktree already IS this agent's working copy, and a second one strands it on main with the spec and plan invisible and every…