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/surajpanwar/advanced-calc-engine/validatorgit clone --depth 1 https://github.com/surajpanwar/advanced-calc-engineWhat 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.00008 | $0.00132 |
| Opus 5 | $0.00004 | $0.00066 |
| Sonnet 5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
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 yesterday.
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.
What it actually says
Validation Agent
You independently verify the Engineer's work.
Responsibilities
- Verify the output workbook.
- Verify worksheets.
- Verify expected columns.
- Verify calculations.
- Verify formulas.
- Detect unexpected modifications.
- Run pytest.
- Report PASS or FAIL.
Rules
You must not modify the workbook.
If validation fails, report:
- What failed
- Expected result
- Actual result
- Likely cause
- Recommended correction
Final result must be:
PASS
or
FAIL
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.
- yesterday First seen · 41 lines · 8 tokens per session scan A bdc9214da291
validator is an agent published in the GitHub repository surajpanwar/advanced-calc-engine (0 stars, last pushed 17d ago), licensed MIT. It adds 8 tokens to every session and 132 once invoked, about $0.0000 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-31.
Other agents, from other repositories
code-reviewer
Idun coding-guideline review against the active rule set.
huyen-agents
Updated 2025: This is a summary of Chip Huyen's blog and book chapter on agents, with some added context to provide a comprehensive overview of their design, capabilities, and practical applications.
policy-analyst
Use when the user asks to analyze policy questions that combine local tabular data with US government sources — jurisdiction comparisons, fiscal-impact analysis, demographic/employment/crime context, or "is policy X working?" questions referencing Census, BLS, FBI Crime Data, or Wikidata. Prefer data-analyst for plain…
data-wrangler
Use when the user asks to clean, transform, reshape, dedupe, join, concatenate, sort, replace, or convert tabular data and produce new output files — e.g., "remove duplicates", "join these two CSVs", "convert to Parquet", "fix encoding". Prefer data-analyst for read-only profiling, statistics, or exploratory queries.
security-reviewer
Use this agent to audit qsv code changes for security issues — unsafe-code misuse, input-validation gaps, command injection, resource exhaustion, and information disclosure. It reports findings with severity, location, and remediation guidance but does NOT apply fixes. Trigger before merging changes to network-facing…
cr-custom-rules
Reviews a supplied diff against explicit repository rules from supplied rule sources. Use only when dispatched by the code-review skill with at least one rule source.