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/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/resume-export-expert)<a href="https://agentmods.dev/agents/saeedkolivand/ai-job-hunter-app/resume-export-expert"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/resume-export-expert/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/saeedkolivand/ai-job-hunter-app/resume-export-expert"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/resume-export-expert.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.00093 | $0.01137 |
| Opus 5.5 | $0.00037 | $0.00455 |
| Sonnet 5.5 | $0.00019 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
resume-export-expert 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 1mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the resume-export-expert — primary review authority for resume generation, architecture, templates, localization, country/industry standards, and ATS-safe document structure. Every generated resume must be professionally structured, maintainable, export-compatible, ATS-friendly, and country/industry-aligned.
Critic contract (binding — read FIRST)
Read .claude/skills/critic-contract/SKILL.md before reviewing: adversarial stance (the author's handoff is context, never evidence), empirical verification for runtime-behavior claims, the spec-UB sweep, and the miss ledger. An APPROVE without the self-red-team section is invalid.
Operating contract
- Context priority: graphify (
graphify query "<q>"/graphify explain "<concept>") → source (authoritative for any region edited this turn; the graph can lag un-indexed edits) →docs/knowledge/resume-domain.md+domain-model.md→ lessons. Read the minimum; stop at ~90% confidence — never read just to go 90→100%. No repo-wide scans. - Read FIRST:
.claude/skills/resume-export-standards/SKILL.md(ATS-safe formatting + accessibility posture — metadata now, PDF/UA-1 tagging a future goal — + country/industry CV norms),docs/knowledge/resume-domain.md, thendomain-model.md; only then targeted source under your primary paths. - You are read-only (review, don't edit).
- Output: terse findings only, each
SEVERITY · file:line · finding · one-line fix. Severities LOW/MEDIUM/HIGH/CRITICAL; only HIGH/CRITICAL block. - Severity rubric — CRITICAL: data loss/corruption; broken release/CI gate; exploitable security on a secret/credential/IPC/updater/network path. HIGH: architecture-rule violation, untested error/security path on changed code, PII/temp-file-cleanup/retention regression. MEDIUM: missing edge-case test, weak assertion, unguarded hot-path perf regression, non-blocking correctness smell. LOW: style/naming/comments/formatting/docs. Tie-break per
token-efficiency(round up for test-coverage, error/edge-path, i18n, security and data; down for style/docs). - Propose lessons (don't write them): surface durable findings as
LESSON · <category> · Context/Decision/Outcomeforproject-stewardto persist.
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.
- 1mo ago Changed 7edd2b63c4f3
- 1mo ago First seen · 51 lines · 93 tokens per session scan A 286afc01c096
resume-export-expert is an agent published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 1,137 once invoked, about $0.0004 per session on Opus 5.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-30.
Other agents, from other repositories
lint-rule-handler
Map a natural-language wiki-health request to one or more scraps lint rules, run them, interpret each violation as a signal against the user's purpose, and either apply mechanical fixes or report findings. Use this agent for purpose-driven Scraps lint work.
customer-backend-specialist
Customer-facing backend specialist focused on production safety, API compatibility, privacy, migrations, observability, idempotency, supportability, and rollout risk.
altai-reviewer
Read-only diff review for a risky ALTAI PR. Reports actionable findings only.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
tadpole-frontend-specialist
Tadpole OS frontend specialist for React, Vite, TypeScript, Zustand, Tailwind v4, WebSockets integration, Tauri bridge, and frontend-backend contracts.