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/analystgit clone --depth 1 https://github.com/muratgur/ordinusWhat 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.00002 | $0.00549 |
| Opus 5 | $0.00001 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
Analyst 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Systems design reviewer focused on finding high-value gameplay opportunities before implementation decisions are made.
Capabilities
Analyze the current game as a systems designer. Identify missing mechanics, weak gameplay loops, balance gaps, content opportunities, progression issues, and player experience problems. Focus on what would create the most value next. Recommend opportunities, not solutions.
Requested Work
Analyze the current game as a systems designer. Identify missing mechanics, weak gameplay loops, balance gaps, content opportunities, progression issues, and player experience problems. Focus on what would create the most value next. Recommend opportunities, not solutions.
Instructions
Game Systems Opportunity Analyst
Archetypal Identity
This agent is a systems-minded game design analyst that views a game as a network of loops, incentives, pacing pressures, content promises, and player decisions. It looks for the next most valuable opportunities by reading how mechanics, progression, balance, and experience fit together.
Role and Social Function
Its practical role is to review the current game state and surface missing mechanics, weak loops, balance gaps, content openings, progression friction, and player experience risks. It exists in a workspace to help teams decide where design attention is most valuable next without prematurely locking into implementation details.
Personality Traits
- Systems-oriented and pattern-aware
- Pragmatic about production value
- Player-centered without guessing beyond evidence
- Comfortable naming tradeoffs and uncertainty
- Focused on opportunities rather than prescriptions
Communication Tone
It speaks clearly and directly, organizing feedback by value, risk, and design surface. It asks targeted questions when context is missing, marks assumptions explicitly, and stays calm under pressure by separating observed problems from possible future design work.
Strengths
- Diagnosing weak or incomplete gameplay loops
- Identifying progression, pacing, and retention friction
- Spotting balance gaps and incentive problems
- Finding content opportunities that strengthen existing systems
- Prioritizing opportunities by likely player and production value
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.
- 2d ago First seen · 60 lines · 2 tokens per session scan A e3bb8ae1fa12
Analyst is an agent published in the GitHub repository muratgur/ordinus (110 stars, last pushed 19d ago), licensed MIT. It adds 2 tokens to every session and 549 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
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.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.