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/saifwarraich/claude-job-applicationsWrote 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/saifwarraich/claude-job-applications/job-analyzer)<a href="https://agentmods.dev/agents/saifwarraich/claude-job-applications/job-analyzer"><img src="https://agentmods.dev/badge/agents/saifwarraich/claude-job-applications/job-analyzer/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/saifwarraich/claude-job-applications/job-analyzer"><img src="https://agentmods.dev/badge/agents/saifwarraich/claude-job-applications/job-analyzer.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.00044 | $0.00580 |
| Opus 5 | $0.00022 | $0.00290 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
job-analyzer 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 47 lines · 44 tokens per session scan A 7a3cfd364731
job-analyzer is an agent published in the GitHub repository saifwarraich/claude-job-applications (1 stars, last pushed 1mo ago), with no licence file. It adds 44 tokens to every session and 580 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
code-reviewer
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…
wp
Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…
wp-security
WordPress security specialist following Human Made and 10up standards. Use for auditing input sanitisation, output escaping, nonce verification, SQL injection, authentication, authorisation, REST API security, and WordPress-specific vulnerabilities. Prioritises exploitable issues in legacy codebases.
a11y
Accessibility auditor for UI code. Use when reviewing components, pages, or user flows for WCAG 2.2 AA/AAA compliance — typically before shipping a UI feature. Covers semantic HTML, keyboard navigation, ARIA, forms, focus management, color contrast, and motion. Framework-aware (React, Vue, WordPress blocks, vanilla…
wp-perf
WordPress performance specialist following Human Made and 10up standards. Use for auditing query performance, caching strategy, asset loading, Core Web Vitals, and database optimization in WordPress projects. Handles both greenfield and inherited legacy codebases.
security
Deep security audit adapted to the project's tech stack. Reads project config to tailor checks. Use before deploys, after adding auth/payment/user-input features, or for periodic review.