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.
npx agentmods add agents/brikev/twd/docs-checkgit clone --depth 1 https://github.com/BRIKEV/twdWhat 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 | $0.00319 | $0.01606 |
| Opus 5 | $0.00160 | $0.00803 |
| Sonnet 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 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.
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 (Testing Web Development) 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.
- 2d ago First seen · 118 lines · 319 tokens per session scan A 67dd49a5b7e8
docs-check is an agent published in the GitHub repository BRIKEV/twd (58 stars, last pushed 4d ago), licensed MIT. It adds 319 tokens to every session and 1,606 once invoked, about $0.0016 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.