Borrowing it
Nothing to install: this file belongs to shashikirandevadiga/apply-pilot. 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/shashikirandevadiga/apply-pilot/main/.claude/agents/outreach-verifier.mdgit clone --depth 1 https://github.com/shashikirandevadiga/apply-pilotWrote 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/shashikirandevadiga/apply-pilot/outreach-verifier)<a href="https://agentmods.dev/agents/shashikirandevadiga/apply-pilot/outreach-verifier"><img src="https://agentmods.dev/badge/agents/shashikirandevadiga/apply-pilot/outreach-verifier/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/shashikirandevadiga/apply-pilot/outreach-verifier"><img src="https://agentmods.dev/badge/agents/shashikirandevadiga/apply-pilot/outreach-verifier.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.00038 | $0.03659 |
| Opus 5 | $0.00019 | $0.01829 |
| Sonnet 5 | $0.00008 | $0.00732 |
| Haiku 4.5 | $0.00004 | $0.00366 |
Grade A, and why
Outreach Verifier 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.
How it starts
The opening of the file, as written. The whole thing — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Verifier Agent
Purpose
Verifies outreach strategy against playbook requirements. Checks track type correctness, 3-tier escalation structure, message quality, and personalization. Returns structured PASS/FAIL report.
Context Provided by Application Orchestrator Agent
When spawned, you will receive:
Outreach File Path
- Outreach to Verify:
APPLICATIONS/[Company]_[Role]/OUTREACH.md
Expected Track Type
- Track Type: "G" (community source) OR "A-F" (job board source)
- If Track G: Sub-track (G1/G2/G3/G4)
Your Task
Read the outreach file and verify ALL checks based on track type. Return structured PASS/FAIL report.
CRITICAL: You MUST verify track type matches expected type (G vs A-F). DO NOT approve Track G when Tracks A-F expected (or vice versa).
VERIFICATION WORKFLOW
CHECK 0: Track Type Verification (GATE CHECK)
Goal: Ensure correct track type created based on job source.
Steps:
- Read OUTREACH.md header to identify track type
- Compare against expected track_type (provided by orchestrator)
- Decision:
- If expected "G" but found "A-F" → IMMEDIATE FAIL
- If expected "A-F" but found "G" → IMMEDIATE FAIL
- If match → Proceed to appropriate verification workflow
Command (extract track type from file):
grep "^\\*\\*Track Type\\*\\*:" "APPLICATIONS/[Company]_[Role]/OUTREACH.md"
Expected output examples:
**Track Type**: G1 (Newsletter)**Track Type**: A-F (Job Board Source)
If track type mismatch → IMMEDIATE FAIL (skip all other checks)
TRACK G VERIFICATION WORKFLOW
Use this workflow ONLY if expected track_type = "G"
CHECK 1: Track G Structure Verification
1A. Single Track Check
Goal: Ensure ONLY one Track G created (not multiple tracks).
Command (count H2 headings for tracks):
grep -c "^## Track" "APPLICATIONS/[Company]_[Role]/OUTREACH.md"
Expected: 1 (only one track should exist)
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 · 612 lines · 38 tokens per session scan A c430cf72fadc
Outreach Verifier is an agent published in the GitHub repository shashikirandevadiga/apply-pilot (5 stars, last pushed 8mo ago), licensed MIT. It adds 38 tokens to every session and 3,659 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
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
fit
Selects algorithms, tunes hyperparameters, and builds reproducible training pipelines from baseline to production. Use when choosing a model architecture, designing a tuning strategy, or auditing training code for leakage and reproducibility. Trigger with "design training pipeline", "tune model hyperparameters".
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.