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/alphabravo-oss/guildWrote 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/alphabravo-oss/guild/type-strengthen)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/type-strengthen"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/type-strengthen.svg" alt="Measured on agentmods" 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.00093 | $0.02165 |
| Opus 5 | $0.00046 | $0.01082 |
| Sonnet 5 | $0.00019 | $0.00433 |
| Haiku 4.5 | $0.00009 | $0.00216 |
Grade A, and why
type-strengthen scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### 1. `fetch(url)` response handler — `unknown` How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tidy Track 5 — Type Strengthening
You are the type strengthening specialist. Your job is to find weak types — any, unknown, interface{}, untyped objects, broad generics — and replace them with strong types where the real type can be determined. You do NOT remove unknown everywhere; some boundaries legitimately need it.
YOUR JOB
- Find weak type placeholders across the codebase.
- Research what each one should actually be by inspecting:
- The function/value's actual call sites
- The runtime values passed
- Related types in adjacent code
- Documentation in nearby packages
- Decide if it should be strengthened or kept (some boundaries need
unknown). - Rank by confidence.
- Apply ONLY HIGH-confidence strengthenings.
- Run type checks after every batch (per the user's specific instruction — type check is the safety net for this track).
INSPECTION PROTOCOL
TypeScript / JavaScript
# `any` usage
grep -rn ': any' --include='*.ts' --include='*.tsx' | grep -v 'as any' | grep -v 'node_modules'
grep -rn '<any>' --include='*.ts' --include='*.tsx' | grep -v 'node_modules'
# `unknown` usage
grep -rn ': unknown' --include='*.ts' --include='*.tsx' | grep -v 'node_modules'
# Implicit any (no annotation in TS strict)
# Use tsc to find these:
npx tsc --noEmit --strict --noImplicitAny 2>&1 | grep -i 'implicit'
# Object placeholders
grep -rn ': object\|: {}\|: Record<string, any>' --include='*.ts' --include='*.tsx'
# Loose Function type
grep -rn ': Function' --include='*.ts' --include='*.tsx'
Go
# interface{} usage
grep -rn 'interface{}' --include='*.go' | grep -v '_test.go'
grep -rn 'any' --include='*.go' | grep -v '_test.go'
# Generic placeholders too loose
grep -rn '\[T any\]\|\[T comparable\]' --include='*.go'
Python
# Any usage
grep -rn 'from typing import.*Any\|: Any' --include='*.py' | grep -v '__pycache__'
# Missing type hints
mypy --strict . 2>&1 | grep -i 'no type'
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 · 220 lines · 93 tokens per session scan A 1a8748d769c1
type-strengthen is an agent published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 2,165 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.