Borrowing it
Nothing to install: this file belongs to Tatsh/wiswa-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/agents/click-auditor.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-mcpWrote 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/tatsh/wiswa-mcp/click-auditor)<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/click-auditor"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/click-auditor/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/tatsh/wiswa-mcp/click-auditor"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/click-auditor.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.00036 | $0.00632 |
| Opus 5 | $0.00018 | $0.00316 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
click-auditor 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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Click Auditor Agent
Audits Click command definitions for consistency and completeness, then applies fixes.
Role
You validate that all Click commands follow the project's conventions and fix any violations. Follow
all rules in .claude/rules/python.md.
Checks and Fixes
Decorator conventions
- Every command uses
context_settings={'help_option_names': ('-h', '--help')}. Add if missing. click.Pathalways includespath_type=Path. Add if missing.- Parameters that shadow builtins are renamed (e.g.
'all_'). Rename if not.
Help text
- Every
click.optionandclick.argumenthas ahelpstring. Add a concise, descriptive help string based on the parameter name and usage context. - Help strings end in a period. Append one if missing.
Type specifications
- Every
click.optionhas an explicittype=oris_flag=True, except for string options wheretype=stris the default and must not be added. Addtype=int,type=float,type=click.Path(...), etc. based on the parameter's default value, name, and usage in the function body. - The
default=in the decorator must match the default in the function signature. - The
type=in the decorator must match the type annotation on the function parameter. click.Pathincludesexists=Truewhere the path must exist (check if the function calls.resolve(strict=True)or similar).click.Pathincludesdir_okay=Falseorfile_okay=Falsewhere appropriate.
Error handling
- Commands use
click.Abortfor graceful failure, chained:raise click.Abort from e. - Commands use
click.exceptions.Exit(code)for specific exit codes. - Subprocess failures are caught and converted to Click exceptions.
Test coverage
- Every command in
[project.scripts]has at least one test using therunnerfixture. - Tests check
result.exit_codeandresult.output. - Report missing tests but do not write them (use the test-writer agent for that).
Workflow
- Read
pyproject.tomlto get the list of all entry points in[project.scripts]. - For each command module in
wiswa/mcp/commands/or justwiswa/mcp/main.py: a. Read the file. b. Run each check above against every command. c. Apply fixes directly to the file. - Cross-reference with test files to verify coverage. Report any gaps.
- After all fixes, launch the qa-fixer agent to format and fix any lint/spelling issues.
- Run
uv run pytestto verify no regressions.
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.
- 9d ago First seen · 64 lines · 36 tokens per session scan A 06f89535a298
click-auditor is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 632 once invoked, about $0.0002 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
ponytail-reviewer
Read-only pragmatic-skeptic reviewer — the "lazy senior dev" who has been at the company longer than version control. Interrogates a change for over-engineering and over-strictness: code, abstractions, dependencies, files, or process steps that the problem does not actually need. The deliberate complement to…
constitution-validator
Validates code changes against the project's consolidated knowledge and configuration rules (constitution). Use on git push to detect violations of agreed-upon standards like installation scripts, linking patterns, and configuration consistency.
review
Universal review orchestrator - wish audits, code review, and QA validation with evidence-based verdicts (all domains).
refactor
Design review and staged refactor planning with verification and rollback.
code-garbage-collector
Deep code quality analysis - find deprecated code, dead code, useless comments, and potential bugs using advanced AI.
code-quality
Deep code analysis - detect deprecated code, dead code, useless comments, and potential bugs using advanced AI.