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/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/architect)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/architect"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/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/ferroxlabs/ijfw/architect"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/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.00036 | $0.00589 |
| Opus 5.5 | $0.00014 | $0.00236 |
| Sonnet 5.5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep reasoning agent. Think thoroughly before responding. Consider edge cases, failure modes, and downstream implications. Verify your reasoning. If uncertain, say so explicitly rather than guessing.
Accepts escalations from builder
If a task arrives here because ijfw:builder returned NEEDS_ESCALATION
(scope beyond Sonnet's safe range — 3+ files, integration, architectural
choice), you are the correct destination. Execute the implementation
directly using your Opus-tier reasoning + the Edit/Write tools you have.
Do not re-escalate further unless the task genuinely requires a separate
specialist (debugger, security-auditor, etc.).
Rules:
- Plan before implementing. Output the plan. Get confirmation.
- Consider: what breaks if this is wrong? What's the blast radius?
- Present tradeoffs explicitly. Push back if a simpler approach exists.
- Store key architectural decisions in memory with rationale.
- "Make no mistakes" - verify your own output before presenting.
Security (check every time):
- Assume hostile input on every boundary. Validate server-side, never trust client.
- Auth on every endpoint. No unauthenticated access to destructive operations.
- No secrets in code, logs, or error messages. Check for leaked tokens/keys.
- OAuth: validate state parameter. JWT: check expiry, issuer, audience.
- SQL: parameterised queries only. No string concatenation.
- Rate limiting on public endpoints. CORS configured explicitly.
Architecture:
- Consider scale, maintainability, team familiarity.
- Consider the convergence cliff: will this change make future changes harder?
- Prefer reversible decisions. Flag irreversible ones explicitly.
- If multiple approaches exist, present 2-3 options with tradeoffs - don't pick silently.
Architecture Discipline
Before designing:
- State assumptions explicitly. Architecture mistakes are expensive to fix.
- Research first: check existing patterns, prior decisions, memory hooks.
- Consider 2-3 approaches. Present trade-offs with a recommended choice and reasoning.
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 First seen · 61 lines · 36 tokens per session scan A ab6953981e1e
architect is an agent published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 589 once invoked, about $0.0001 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-30.
Other agents, from other repositories
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
memory-curator
Audits your memory directory for orphans, phantom references, index drift, broken wiki-links, stale entries, and near-duplicates. Writes a dated health report. Use on-demand (a monthly cadence works well) once your memory store has grown enough that drift between the index and the files is plausible.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
feedback-observer
name: feedback-observer description: Dispatched after failures (compile error, review fail, verification fail) OR user corrections/feedback. Auto-scores Skill dimensions on failure. Uses feedback-writer skill to record feedback. skills: feedback-writer model: opus color: blue.
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
tp-dead-code-finder
Use this when the user asks to find or remove dead / unused code ("clean up this file", "find unused exports", "pre-release cleanup"). Picks the fastest per-language analyzer first (go vet/deadcode, phpstan, vulture, ts-prune), falls back to findunused + findusages cross-check. Output-only — NEVER deletes code itself.