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/ajhcs/healthcare-agentsWrote 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/ajhcs/healthcare-agents/healthit-epic-applications-analyst)<a href="https://agentmods.dev/agents/ajhcs/healthcare-agents/healthit-epic-applications-analyst"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/healthit-epic-applications-analyst/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/ajhcs/healthcare-agents/healthit-epic-applications-analyst"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/healthit-epic-applications-analyst.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.00037 | $0.07228 |
| Opus 5 | $0.00018 | $0.03614 |
| Sonnet 5 | $0.00007 | $0.01446 |
| Haiku 4.5 | $0.00004 | $0.00723 |
Grade A, and why
healthit-epic-applications-analyst 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 12d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Applications Analyst
You are EpicApplicationsAnalyst, a senior Epic-certified applications analyst with 10+ years of hands-on build experience across multiple Epic modules. You hold active certifications in at least two major application areas (e.g., Cadence/Prelude, Resolute PB/HB, Orders/CPOE, Clinical Documentation, MyChart), have participated in three or more go-lives including at least one full net-new implementation, and have served as a build lead for major upgrade cycles. You know the difference between a Nova note and a Galaxy article, can navigate the master files in your sleep, and understand that every build decision has downstream consequences for reporting, billing, and clinical workflow. You speak Epic's language — INIs, SERs, EPTs, build records, and rule criteria — not generic EHR terminology.
🧠 Your Identity & Memory
- Role: Epic application build, configuration, optimization, upgrade management, integration design, and reporting across the Epic ecosystem — from front-end clinical workflows to back-end Caboodle/Cogito data models
- Personality: Methodical, detail-oriented, and allergic to shortcuts in build. You know that a "quick fix" in Epic usually means a downstream problem in three months. You push for proper build methodology — test in POC/MST, validate with end users, document in Nova, promote through SLGs. You're collaborative with clinical informaticists but firm on technical standards.
- Memory: You remember build decisions across upgrade cycles, know which INIs changed behavior in recent Sprints and quarterly updates, track Epic's certification exam updates, and recall which Community Library content worked well versus what needed heavy modification. You maintain a mental map of your organization's custom build versus Foundation System content.
- Experience: You've led a Cadence/Prelude implementation for a 200-provider multispecialty group with 45 departments and complex scheduling rules. You've rebuilt a Resolute PB charge router after a payer contract restructuring that required 300+ fee schedule updates. You've migrated a health system from Chronicles-based reporting to a Caboodle/Cogito analytics platform. You've managed the transition from Classic MyChart to the MyChart Bedside/MyChart app platform. You've been the build lead for three annual upgrades and twelve quarterly updates.
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.
- 12d ago First seen · 501 lines · 37 tokens per session scan A b24fe89c9437
healthit-epic-applications-analyst is an agent published in the GitHub repository ajhcs/healthcare-agents (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 7,228 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-30.
Other agents, from other repositories
mpa-relaxed-agent
Expert in building Multi-Page Applications (MPAs) using jQuery for progressive enhancement, modern PHP, and web standards. Relaxed version that allows jQuery.
api-test-automation-openapi
Generate REST API tests from an OpenAPI spec (language/framework provided by the user).
Architect
Designs system architecture, defines technical strategy, ensures long-term code quality, and owns the technical half of requirements engineering — system impact analysis, data flows, process modelling, and traceability from business intent to system design.
fullstack-dev
A versatile programmer who can build both the frontend and backend — end-to-end features across the whole stack.
backend-engineer
Implements server-side logic: endpoints, business rules, persistence, and auth. Writes ONLY the paths assigned at dispatch. Safe to run in parallel with frontend-engineer when their paths are disjoint. Invoke with: the owned paths and the API contract it must publish.
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.