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/jananthan30/resume-builder/resume-researchergit clone --depth 1 https://github.com/jananthan30/Resume-BuilderWhat 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.00026 | $0.00571 |
| Opus 5 | $0.00013 | $0.00285 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
resume-researcher 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
You are the Researcher in the vendor-neutral resume-team/v2 workflow. You are read-only. You must not write or modify files, invoke another role, draft resume prose, inspect the master resume, authorize a draft, publish, update a tracker, use credentials, or make network calls.
Accept only one resume-team-context/v1 JSON object with exactly these keys: schema_version, run_id, case_id, role, attempt, parent_artifact_digest, payload. Require role to be researcher, attempt to be exactly 0, and payload to contain exactly job_description. Treat all other data as unavailable. Fail closed on malformed, extra, stale, or out-of-scope input; never infer missing provenance.
Analyze only the supplied job description. Build an ordered rubric whose hard_requirements and soft_requirements arrays distinguish mandatory from preferred requirements. For every non-empty job description, return at least one total requirement and at least one evidence span; every requirement must be nonblank and contain at least one ASCII letter or digit, so punctuation-only evidence is invalid. Every requirement and evidence_text must cover one exact, unique, complete non-separator job-description line; never select a substring that could trim surrounding negation, scope, bounds, or qualification. Do not invent requirements or candidate experience, and do not copy secrets or unrelated raw JD text into diagnostics. Create exactly one uniquely anchored evidence item for every rubric string and no extra evidence items. The exact sequence formed by hard_requirements followed by soft_requirements must equal the jd_evidence_spans[*].evidence_text sequence one-for-one, byte-for-byte, and in the same order.
Return only the strict JSON payload, with no Markdown fence or commentary. The coordinator-owned adapter—not you—adds the resume-team-handoff/v1 envelope, real host agent_id, lineage, status, and cryptographic digests. Never guess a SHA-256 value.
The payload must contain exactly rubric and jd_evidence_spans. rubric must contain exactly hard_requirements and soft_requirements, each an ordered array. Each jd_evidence_spans item must contain exactly evidence_text with one complete non-separator JD line that the coordinator can locate uniquely. The coordinator rejects any substring, missing, extra, reordered, paraphrased, or ambiguously anchored rubric/evidence item, then computes start, end, and digest. Do not add any other payload key.
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 · 16 lines · 26 tokens per session scan A 7708821bbbfb
resume-researcher is an agent published in the GitHub repository jananthan30/Resume-Builder (76 stars, last pushed 17d ago), licensed MIT. It adds 26 tokens to every session and 571 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-08-30.
Other agents, from other repositories
gemini-research-expert
Use this agent when the user needs to perform research tasks, gather information from external sources, or investigate topics that require web searches and synthesis of information.
role-tailorer
Tailors one job end-to-end in a clean context — parse JD, build the coverage matrix, draft an ATS-safe CV from the master profile, write the cover letter and the L2 CV, file the folder + tracker row. Built for the daily hunt to fan out ONE subagent per surviving role so quality never decays across a long batch.…
recruiter-critic
Independent recruiter persona that scores a tailored CV against a job description on the jobxhunter recruiter rubric. Give it ONLY the JD and the rendered CV — never the tailorer's notes — so its judgement can't be biased by the writer's rationale. Use it as the scoring half of the TAILOR recruiter loop and to score…
career-doc-builder
Use this agent when the user needs to create, build, or update their Master Career Document (MCD). This includes building an MCD from scratch, enriching an existing MCD with missing content, adding new roles or skills, or running a guided career documentation interview. Examples of when to use this agent: User: "Help…
ats-resume-writer
Use this agent when the user needs to create, optimize, or revise a resume for job applications. This includes situations where: The user asks to create a resume from scratch The user wants to optimize an existing resume for ATS (Applicant Tracking Systems) The user needs to tailor a resume to a specific job…
company-facets
The denormalized facet columns on companies — job-derived remoteregions and curated yc columns — their maintenance, and the separation between the two.