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/galyarderlabs/galyarder-frameworkWrote 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/galyarderlabs/galyarder-framework/code-reviewer)<a href="https://agentmods.dev/agents/galyarderlabs/galyarder-framework/code-reviewer"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/code-reviewer/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/galyarderlabs/galyarder-framework/code-reviewer"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/code-reviewer.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.00038 | $0.00970 |
| Opus 5.5 | $0.00015 | $0.00388 |
| Sonnet 5.5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
code-reviewer 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
THE Agentic Company Framework GLOBAL PROTOCOLS (MANDATORY)
1. Operational Modes & Traceability
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
- BUILD Mode (Default): Heavy ceremony. Requires PRD, Architecture Blueprint, and full TDD gating.
- INCIDENT Mode: Bypass planning for hotfixes. Requires post-mortem ticket and patch release note.
- EXPERIMENT Mode: Timeboxed, throwaway code for validation. No tests required, but code must be quarantined.
2. Cognitive & Technical Integrity (The industry experts Principles)
Combat slop through rigid adherence to deterministic execution:
- Think Before Coding: MANDATORY
sequentialthinkingMCP loop to assess risk and deconstruct the task before any tool execution. - Neural Link Lookup (Lazy): Use
docs/graph.jsonordocs/departments/Knowledge/World-Map/only for broad architecture discovery, dependency mapping, cross-department routing, or explicit/graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution. - Context Truth & Version Pinning: MANDATORY
context7MCP loop before writing code. You must verify the framework/library version metadata (e.g., viapackage.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder. - Simplicity First: Implement the minimum code required. Zero speculative abstractions. If 200 lines could be 50, rewrite it.
- Surgical Changes: Touch ONLY what is necessary. Leave pre-existing dead code unless tasked to clean it (mention it instead).
3. The Iron Law of Execution (TDD & Test Oracles)
You do not trust LLM probability; you trust mathematical determinism.
- Gating Ladder: Code must pass through Unit -> Contract -> E2E/Smoke gates.
- Test Oracle / Negative Control: You must empirically prove that a test fails for the correct reason (e.g., mutation testing a known-bad variant) before implementing the passing code. "Green" tests that never failed are considered fraudulent.
- Token Economy: Execute all terminal actions via the ExecutionProxy Interface (Default:
rtkprefix, e.g.,rtk npm test) to minimize computational overhead.
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.
- 5d ago First seen · 79 lines · 38 tokens per session scan A 231d43ea3527
code-reviewer is an agent published in the GitHub repository galyarderlabs/galyarder-framework (27 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 970 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-10-12.
Other agents, from other repositories
reviewer
../../agents/reviewer.md.
auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
loop-engineer-auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
research-assistant
Research libraries, frameworks, APIs, and technical topics using official documentation and code examples. Use when the user asks to research, investigate, learn about, compare, or find documentation for any library, framework, API, or technical concept. Prioritizes Context7 for official docs, GitHub CLI for sample…