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 commands/williamzujkowski/mcp-standards-server/querygit clone --depth 1 https://github.com/williamzujkowski/mcp-standards-serverWhat 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.00000 | $0.02384 |
| Opus 5 | $0.00000 | $0.01192 |
| Sonnet 5 | $0.00000 | $0.00477 |
| Haiku 4.5 | $0.00000 | $0.00238 |
Grade A, and why
query 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
query Command
Query standards based on project context and requirements.
Synopsis
mcp-standards query [options]
Description
The query command allows you to search and retrieve applicable standards based on your project's context, technology stack, and specific requirements. It uses intelligent matching and can provide results in various formats.
Options
--project-type <type>
Specify the type of project.
mcp-standards query --project-type web-application
--framework <name>
Specify frameworks being used.
mcp-standards query --framework react --framework express
--language <name>
Specify programming languages.
mcp-standards query --language javascript --language typescript
--requirements <req>
Specify special requirements.
mcp-standards query --requirements accessibility --requirements security
--tags <tag>
Filter by specific tags.
mcp-standards query --tags frontend --tags testing
--format <format>
Output format (text, json, yaml, markdown).
mcp-standards query --format json
--detailed
Include detailed standard content.
mcp-standards query --detailed
--token-budget <number>
Limit response to token budget.
mcp-standards query --token-budget 4000
--semantic
Use semantic search for natural language queries.
mcp-standards query --semantic "How do I implement authentication in React?"
Examples
Basic Query
mcp-standards query --project-type web-application --framework react
Output:
Applicable Standards Found: 7
1. React 18 Patterns (react-18-patterns.yaml)
Tags: frontend, react, javascript, components
Priority: HIGH
Summary: Modern React patterns including hooks, Server Components, and performance optimization
2. JavaScript ES2025 Standards (javascript-es2025.yaml)
Tags: javascript, ecmascript, language
Priority: HIGH
Summary: Modern JavaScript language features and best practices
3. Web Accessibility Standards (wcag-2.2-accessibility.yaml)
Tags: accessibility, a11y, web
Priority: MEDIUM
Summary: WCAG 2.2 compliance guidelines and ARIA patterns
4. Frontend Testing Standards (frontend-testing.yaml)
Tags: testing, frontend, jest, react-testing-library
Priority: MEDIUM
Summary: Testing patterns for React components and applications
[... more results ...]
Use --detailed to see full content or --format json for programmatic access
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 · 425 lines · 0 tokens per session scan A ead9d1fd22c2
query is a command published in the GitHub repository williamzujkowski/mcp-standards-server (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,384 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.