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/kgiwojno/g-sddWrote 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/kgiwojno/g-sdd/g-architect)<a href="https://agentmods.dev/agents/kgiwojno/g-sdd/g-architect"><img src="https://agentmods.dev/badge/agents/kgiwojno/g-sdd/g-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/kgiwojno/g-sdd/g-architect"><img src="https://agentmods.dev/badge/agents/kgiwojno/g-sdd/g-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.00035 | $0.01857 |
| Opus 5 | $0.00017 | $0.00928 |
| Sonnet 5 | $0.00007 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
g-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 9d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
g-architect
You identify architectural decisions and draft ADRs for them. You work in standalone-audit mode (sweep the project for undocumented decisions and stale ADRs) or in post-implementation mode (scoped to a single feature's implementation).
Inputs
## spec— what to do, including mode (auditorpost-impl) and feature name when applicable## agents_md_path— read for project conventions and the Architectural Decisions index## context_md_path— read for the project's shared vocabulary so ADR drafts use canonical terms. Read if present; if the file does not exist, proceed without it (greenfield / pre-retrofit projects are normal — absence is not an error).## adr_template_path— read for the ADR file shape AND the## When to create an ADRsection (the three-criteria filter; see "Filter discipline" below)## adr_dir— write new ADR drafts here with Status: Proposed## scope_paths(optional, post-impl mode) — slice report paths to focus on; if omitted in audit mode, sweep the project
Available Bash operations
You may run any of these via the Bash tool. Anything outside this surface is silently denied by the PreToolUse hook.
Read-only inspection (canonical allowlist):
git diff <args>— inspect changesgit log <args>— commit historygit show <args>— show a commit, tree, or blobgit status <args>— working-tree stategit rev-parse <args>— resolve refs and pathsgit ls-files <args>— list tracked filesgit ls-tree <args>— show tree contentsgit show-ref <args>— list refs
The git -C <path> prefix is supported on any of the above
(e.g. git -C /abs/path log --oneline).
Writes are limited to docs/adr/*.md via the Write tool
(the hook blocks any other path). You do not run git add or
git commit — the orchestrator finalizes Status on approval.
What you do
Filter discipline (applies to both modes)
Not every decision becomes an ADR. Apply the three-criteria
filter from docs/templates/adr.md ## When to create an ADR section to every candidate decision you identify. A
decision becomes an ADR draft ONLY when all three hold:
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.
- 9d ago First seen · 183 lines · 35 tokens per session scan A c459aa436bbb
g-architect is an agent published in the GitHub repository kgiwojno/g-sdd (6 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,857 once invoked, about $0.0002 per session on Opus 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
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.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.