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 skills/ankitforcode/medify-mcp-server/medify-mcp-maintainnpx skills add ankitforcode/medify-mcp-server --skill medify-mcp-maintaingit clone --depth 1 https://github.com/ankitforcode/medify-mcp-serverWrote 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/skills/ankitforcode/medify-mcp-server/medify-mcp-maintain)<a href="https://agentmods.dev/skills/ankitforcode/medify-mcp-server/medify-mcp-maintain"><img src="https://agentmods.dev/badge/skills/ankitforcode/medify-mcp-server/medify-mcp-maintain.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.00754 |
| Opus 5 | $0.00026 | $0.00377 |
| Sonnet 5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
medify-mcp-maintain 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain medify-mcp-server
Layout
src/
index.ts # stdio MCP server + tool switch
medify/client.ts # login, cookie jar, fetchJson / fetchJsonApi
medify/endpoints.ts # mock cache, topic + script detail fetch
medify/normalize.ts # scores-stats → MockResult, merge/dedupe
analysis/ # trends, topics, timing, recommendations
tools/ # MCP schemas + handlers
.cursor/skills/
medify-ucat-analysis/ # end-user analysis skill (keep in sync with tools)
medify-mcp-maintain/ # this skill
Hard rules for Medify HTTP
- Do not treat
/m/ucat/exams/completedHTML as the score API — it is an Ember SPA shell.Accept: application/jsonoften returns 406. - Do use:
GET /courses-api/mock-scores-stats?course=ucat—Accept: application/json(scaled series)GET /courses-api/mock-exam-scripts?filter[completed]=true&filter[course]=ucat—Accept: application/vnd.api+jsonGET /courses-api/mock-exam-scripts/:id?include=questions.question-set— JSON:API detail + timingsGET /courses-api/courses/ucat/topic-performances?timing=0—Accept: application/json
- Auth probe for
check_connection= mock-scores-stats, not HTML routes. - Cookie jar may authenticate without env vars; keep that behaviour.
Adding or changing a tool
- Implement pure analysis in
src/analysis/when possible (unit-testable). - Add fetch helpers on
MedifyScoreServiceinendpoints.tsif new HTTP is needed. - Add Tool schema + handler in
src/tools/. - Register in
src/index.ts(TOOLS+switch). - Bump
package.jsonversion; keep serverversioninindex.tsaligned. - Update skills in the same change:
.cursor/skills/medify-ucat-analysis/SKILL.md(workflow / tool map).cursor/skills/medify-ucat-analysis/tools-reference.md(args + defaults)
- Update root
README.mdtools table if the public surface changed. npm test && npm run build.
Analysis modules
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.
- 4d ago First seen · 65 lines · 53 tokens per session scan A 4b00e2bfeebc
medify-mcp-maintain is a skill published in the GitHub repository ankitforcode/medify-mcp-server (1 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 754 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…