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/onlygian/G-ForgeWrote 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/onlygian/g-forge/pygame-architect)<a href="https://agentmods.dev/agents/onlygian/g-forge/pygame-architect"><img src="https://agentmods.dev/badge/agents/onlygian/g-forge/pygame-architect/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/onlygian/g-forge/pygame-architect"><img src="https://agentmods.dev/badge/agents/onlygian/g-forge/pygame-architect.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.00049 | $0.01142 |
| Opus 5.5 | $0.00020 | $0.00457 |
| Sonnet 5.5 | $0.00010 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
pygame-architect 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 1mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago Changed · -18 lines 47b6818c3ea3
- 1mo ago First seen · 148 lines · 49 tokens per session scan A aea5106abba9
pygame-architect is an agent published in the GitHub repository onlygian/G-Forge (4 stars, last pushed 10d ago), licensed GPL-3.0. It adds 49 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-08-31.
Other agents, from other repositories
ccf-spec-checker
Use when /ccf:check reviews a finished implementation. Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
ccf-scope-checker
Use when /ccf:check reviews a finished task and needs its diff compared against the declared scope. Fresh-context SCOPE reviewer run by /ccf:check in parallel with ccf-spec-checker - checks only whether the diff matches the task's declared scope (files outside Files to touch, criteria with no matching change, changes…
ccf-finding-refuter
Use when /ccf:check has merged its review reports and at least one FAIL: line exists. Fresh-context adversarial reviewer that tries to refute each FAIL: with quoted evidence (the code verbatim at that location, or a command and its real output) and returns REFUTED or STANDS per finding. Read-only, adds no new…
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
pr-reviewer
Read-only, separate-context general code reviewer. It reviews a changed diff for correctness, regressions, maintainability, test coverage, and API/contract hygiene, and emits categorized findings (Block / Risk / Nit) for the operator to act on. Use it when an atom changes code and you want a fresh review pass the…