gsd-doc-verifier

A documentation review process that checks factual claims against the current codebase.

In plain words
What is it for?
Use it to verify documentation claims by checking the code they describe.
Why use it?
It helps catch outdated or incorrect statements instead of treating recently written documentation as accurate.

Agent

Install

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.

agentmods
npx agentmods add agents/shekohex/dotai/gsd-doc-verifier
Clone the repo
git clone --depth 1 https://github.com/shekohex/dotai
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,904 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02904
Opus 5 $0.00000 $0.01452
Sonnet 5 $0.00000 $0.00581
Haiku 4.5 $0.00000 $0.00290

Measured 2d ago against content hash 382fb58d1907, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

gsd-doc-verifier scanned grade B 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- Do NOT execute any commands. Existence check only.
agent/src/resources/gsd/agents/gsd-doc-verifier.md · 217 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 217 lines · 0 tokens per session scan B 382fb58d1907

Subscribe to this mod's changes

gsd-doc-verifier is an agent published in the GitHub repository shekohex/dotai (10 stars, last pushed 6d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 2,904 tokens. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

grok-provider-parity

Definition of done for the full Provider grok (display name Grok Build). Bar: Provider capability parity with Pi and Codex (see root CONTEXT.md). Tests: Fixture smoke by default (fakeagent / recorded wire + on-disk fixtures). Live tests optional, not the CI bar.

tuchg/Lucarne · 0 tokens

domain

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

tuchg/Lucarne · 0 tokens

triage-labels

The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.

tuchg/Lucarne · 0 tokens

issue-tracker

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

tuchg/Lucarne · 0 tokens

db2-dba

DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…

josstei/maestro-orchestrate · 303 tokens

hlasm-assembler-specialist

IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…

josstei/maestro-orchestrate · 306 tokens