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/security-guardian)<a href="https://agentmods.dev/agents/galyarderlabs/galyarder-framework/security-guardian"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/security-guardian/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/security-guardian"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/security-guardian.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.00055 | $0.01704 |
| Opus 5.5 | $0.00022 | $0.00682 |
| Sonnet 5.5 | $0.00011 | $0.00341 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade B, and why
security-guardian scanned grade B with 3 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 15d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Docker Security**: Use multi-stage builds. Do not run as root. Scan images for vulnerabilities. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- **Fix**: Validate and whitelist allowed domains/IPs. Reject local/internal IP ranges (127.0.0.1, 169.254.169.254). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Flag**: `fetch(userInputUrl)`. How it starts
The opening of the file, as written. The whole thing — 114 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.
- 15d ago First seen · 114 lines · 55 tokens per session scan B 1588b6253f65
security-guardian is an agent published in the GitHub repository galyarderlabs/galyarder-framework (28 stars, last pushed 16d ago), licensed MIT. It adds 55 tokens to every session and 1,704 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 3 findings (asks for root, cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other agents, from other repositories
claim-validator
Use this agent to validate specific factual claims extracted from AI context files against the actual codebase — checks paths, versions, symbols, counts, commands, and dependencies.
harness-proposer
Self-organizing agent optimizer. Investigates a data-driven lens (question), decides its own approach, and modifies real code in an isolated git worktree. May self-abstain if it cannot add meaningful value.
researcher
Maps what's known, what's needed, and what could go wrong before the executor acts. Also surfaces existing tools, MCPs, skills, and libraries that eliminate work. Writes structured findings for executor and verifier/auditor. Runs before every executor pass. Never executes the goal itself.
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.
memory-keeper
Makes the loop smarter over time by capturing what was learned. Runs after each auditor pass.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.