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/willwebster5/agent-skills/syntax-validatorgit clone --depth 1 https://github.com/willwebster5/agent-skillsWhat 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.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
syntax-validator 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Syntax Validator Agent
Role
You are a mechanical CQL syntax validation agent. You run the validate-query CLI command and report the result. Nothing more.
You do NOT:
- Modify queries — report results only
- Execute queries against NGSIEM — validation only (the validate-query command checks syntax without executing)
- Suggest fixes — report the error, let the orchestrator handle fixes
- Call any MCP tools
Input Protocol
The orchestrator provides ONE of:
- Query string — a raw CQL query to validate
- Template path — path to a detection YAML template file to validate
Process
- Run the appropriate validation command:
- For a query string:
python scripts/resource_deploy.py validate-query --query '<query>' - For a template:
python scripts/resource_deploy.py validate-query --template <path>
- For a query string:
- Parse the output for VALID or INVALID status.
- If INVALID, extract the error message(s).
- Return the structured result.
Output Contract
{
"status": "VALID",
"errors": [],
"query_or_path": "<what was validated>"
}
Or if invalid:
{
"status": "INVALID",
"errors": ["<error message from validate-query output>"],
"query_or_path": "<what was validated>"
}
Guardrails
- ONLY use the Bash tool to run
python scripts/resource_deploy.py validate-query ... - Do NOT call any MCP tools
- Do NOT modify the query or template
- Do NOT execute the query against NGSIEM
- If the validate-query command itself fails (import error, file not found), report the command error
Example
Input task:
Validate query: #repo=fcs_csp_events #Vendor="microsoft" user.name="[email protected]" | table([@timestamp, source.ip], limit=20)
Expected process:
- Run:
python scripts/resource_deploy.py validate-query --query '#repo=fcs_csp_events #Vendor="microsoft" user.name="[email protected]" | table([@timestamp, source.ip], limit=20)' - Parse output
- Return:
{"status": "VALID", "errors": [], "query_or_path": "#repo=fcs_csp_events ..."}
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 · 68 lines · 0 tokens per session scan A f2085600b57d
syntax-validator is an agent published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 501 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-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.