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.
git clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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/rojim666/sztucode/prompthookevaluator)<a href="https://agentmods.dev/agents/rojim666/sztucode/prompthookevaluator"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/prompthookevaluator/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/rojim666/sztucode/prompthookevaluator"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/prompthookevaluator.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.00017 | $0.00033 |
| Opus 5 | $0.00009 | $0.00016 |
| Sonnet 5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00003 |
Grade A, and why
promptHookEvaluator 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 today.
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
prompt-hook-evaluator-instructions
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.
- today First seen · 7 lines · 17 tokens per session scan A 3eb499572f01
promptHookEvaluator is an agent published in the GitHub repository rojim666/SztuCode (64 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 33 once invoked, about $0.0001 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-09-12.
Other agents, from other repositories
dependencylibraries-analysis
Start codebase analysis. Analyze single entity/action only. Return detailed analysis, recommendations, implementation guidance, usage examples. Prefer dependencylibraries-related-files-search first. Provide all relevant context (files, paths, symbols, imports, etc.). One topic or one context per request → wait for the…
dependencylibraries-related-files-search
Start related-file discovery. Find files relevant to single entity/action before dependencylibraries-analysis. Provide all relevant context (files, paths, symbols, imports, etc.). One topic or one context per request → wait for the result → send the next request! Instead "Find X, Y, Z, etc." you MUST "Find X.", wait…
dependencylibraries-list-libraries
Return the public names of local libraries/codebases available for analysis. Provide dependencylibraries-related-files-search and/or dependencylibraries-analysis with an approptiate name from this list.
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).