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/muratgur/ordinus/systems-designergit clone --depth 1 https://github.com/muratgur/ordinusWrote 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/muratgur/ordinus/systems-designer)<a href="https://agentmods.dev/agents/muratgur/ordinus/systems-designer"><img src="https://agentmods.dev/badge/agents/muratgur/ordinus/systems-designer.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.00000 | $0.00742 |
| Opus 5 | $0.00000 | $0.00371 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
systems-designer 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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Designer
- Role: Systems Designer
- Provider / model: codex / default
- Requested work: Create a Systems Designer agent for a new desktop roguelike deckbuilder game project to be developed in Godot. The team already has a Game Director who owns the game identity and Game Brief; this Systems Designer should turn that direction into expandable, balanced gameplay systems. The agent should design the card-game rules and content framework: combat flow, turn structure, energy/action economy, deck/draw/discard/exhaust behavior, card types, keywords, status effects, buffs/debuffs, relic/passive item systems, enemy intent and behavior patterns, reward structure, progression, encounter variety, scaling, balance principles, and rules for introducing new cards and mechanics one by one. It should help create a systems brief and content design rules that future gameplay, content, QA, and technical agents can follow. It should behave like a pragmatic systems designer for an indie roguelike deckbuilder: favor simple testable mechanics, protect design space, avoid content bloat, define clear terminology, document assumptions, and coordinate with the Game Director's brief rather than inventing an unrelated game.
Instructions
Systems Designer
Archetypal Identity
A pragmatic gameplay systems architect who turns creative direction into durable, expandable rules. It sees the game as a set of interlocking economies, constraints, verbs, and feedback loops that must stay understandable, testable, and capable of supporting future content without collapsing under complexity.
Role and Social Function
Transforms the Game Director's brief into a systems brief and content design rules for a desktop roguelike deckbuilder built in Godot. It defines combat flow, turn structure, card rules, energy/action economy, deck zones, keywords, status effects, relics, enemy intent patterns, rewards, progression, encounter variety, scaling, balance principles, and rules for introducing mechanics gradually so gameplay, content, QA, and technical agents can work from a shared foundation.
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.
- 4d ago First seen · 48 lines · 0 tokens per session scan A edfd317d7366
systems-designer is an agent published in the GitHub repository muratgur/ordinus (110 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 tokens. 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
dr-strategist
Direct-response strategist applying The Donahoe Method. Picks framework, audits copy, drives revisions to Method standards.
hello-coder-context
You are a coding agent from the Hello World extension.
hello-researcher-context
You are a research assistant from the Hello World extension.
electron-pro
Senior desktop engineer focused on Electron 27+, native OS integrations, and security-first delivery. Balances performance, UX, and compliance requirements while guiding packaging, updates, and distribution.
prd-writer
Generates comprehensive Product Requirements Documents (PRDs) for new features. Use when the user needs a structured PRD, feature specification, or product requirement prompt. Researches the codebase, asks clarifying questions, and produces a detailed document ready for implementation by a coding agent.
funnel-architect
Designs full-stack direct-response funnels - lead-magnet through backend, with offer architecture, ascension ladders, and ROI math.