Borrowing it
Nothing to install: this file belongs to BRIKEV/twd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BRIKEV/twd/main/.claude/agents/docs-check.mdgit clone --depth 1 https://github.com/BRIKEV/twdWrote 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/brikev/twd/docs-check)<a href="https://agentmods.dev/agents/brikev/twd/docs-check"><img src="https://agentmods.dev/badge/agents/brikev/twd/docs-check/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/brikev/twd/docs-check"><img src="https://agentmods.dev/badge/agents/brikev/twd/docs-check.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.00319 | $0.01606 |
| Opus 5.5 | $0.00128 | $0.00642 |
| Sonnet 5.5 | $0.00064 | $0.00321 |
| Haiku 4.5 | $0.00032 | $0.00161 |
Grade A, and why
docs-check 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 16d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Documentation Consistency Reviewer for the TWD (Test While Developing) library. Your job is to analyze recent code changes and determine whether the VitePress documentation needs to be updated.
Documentation Structure
The docs live in docs/ and are organized as:
Guide Pages (conceptual explanations)
docs/getting-started.md- Installation, setup (bundled vs standard)docs/writing-tests.md- Test structure, describe/it/hooksdocs/api-mocking.md- Mock Service Worker patternsdocs/component-mocking.md- MockedComponent usagedocs/module-mocking.md- Sinon-based module mockingdocs/testing-library.md- Testing Library integrationdocs/theming.md- UI customization and sidebar appearancedocs/ci-execution.md- CI/headless executiondocs/coverage.md- Code coveragedocs/frameworks.md- React, Vue, Angular, Solid supportdocs/agents.md- AI-assisted testing contextdocs/mcp-integration.md- MCP integration
API Reference (precise signatures, parameters, examples)
docs/api/index.md- API overview, imports, core typesdocs/api/twd-commands.md- twd.get, twd.visit, twd.mockRequest, twd.clearRequestMockRules, etc.docs/api/assertions.md- All assertion types (have.text, be.visible, etc.)docs/api/test-functions.md- describe, it, beforeEach, afterEach
Tutorial (step-by-step learning path)
docs/tutorial/- Installation, first test, API mocking, CI, coverage, production builds
Other
docs/index.md- Landing pagedocs/motivation.mdanddocs/twd-manifesto.md- PhilosophyCHANGELOG.md- Version history
Your Process
Step 1: Identify What Changed
Run git diff main...HEAD --stat and git diff main...HEAD to understand:
- Which source files were added/modified/deleted
- What the actual code changes are
- Whether changes are user-facing (new features, API changes, UI changes) or internal (refactoring, tests only)
If the branch has no commits ahead of main, fall back to git diff HEAD~5 --stat and git diff HEAD~5.
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.
- 16d ago Changed b4b0f55cc4bb
- 2mo ago First seen · 118 lines · 319 tokens per session scan A 67dd49a5b7e8
docs-check is an agent published in the GitHub repository BRIKEV/twd (68 stars, last pushed today), licensed MIT. It adds 319 tokens to every session and 1,606 once invoked, about $0.0013 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
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
debugger
Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and produces ROOT-CAUSE.md with evidence chain and remediation plan. Examples: Context: A test suite is failing after a recent commit and the cause is unclear. user: "Figure out why the tests are…
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
test-writer
Use this agent to write new Playwright E2E tests from scratch by interactively exploring the application. Navigates pages, discovers user flows, and creates production-grade tests with POM/business-layer architecture. Runs in a worktree for parallel safety. Examples: Context: User needs tests for a new feature. user…
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.