medify-mcp-maintain

medify-mcp-maintain is a skill for Claude Code, Codex, Cursor from ankitforcode/medify-mcp-server. It costs 53 tokens per session (754 once invoked), scanned A, original, MIT.

A maintenance guide for the Medify courses API client and its MCP tools. Medify is an online study platform, and an MCP server lets an AI assistant call these course and score functions.

In plain words
What is it for?
Use it when changing Medify API requests, score handling, analysis features, MCP tool wiring, related skills, or the project README.
Why use it?
It keeps authentication, score retrieval, data conversion, analysis modules, tools, and documentation aligned when the codebase changes.

Skill for Claude CodeCodexCursor

Install

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.

agentmods
npx agentmods add skills/ankitforcode/medify-mcp-server/medify-mcp-maintain
Any agent
npx skills add ankitforcode/medify-mcp-server --skill medify-mcp-maintain
Clone the repo
git clone --depth 1 https://github.com/ankitforcode/medify-mcp-server

Made for: Claude Code, Codex, Cursor.

Wrote 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.

agentmods badge for medify-mcp-maintain

README.md
[![agentmods](https://agentmods.dev/badge/skills/ankitforcode/medify-mcp-server/medify-mcp-maintain.svg)](https://agentmods.dev/skills/ankitforcode/medify-mcp-server/medify-mcp-maintain)
Your own site
<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>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 4b00e2bfeebc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/skills/medify-mcp-maintain/SKILL.md · 65 lines

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

  1. Do not treat /m/ucat/exams/completed HTML as the score API — it is an Ember SPA shell. Accept: application/json often returns 406.
  2. Do use:
    • GET /courses-api/mock-scores-stats?course=ucatAccept: application/json (scaled series)
    • GET /courses-api/mock-exam-scripts?filter[completed]=true&filter[course]=ucatAccept: application/vnd.api+json
    • GET /courses-api/mock-exam-scripts/:id?include=questions.question-set — JSON:API detail + timings
    • GET /courses-api/courses/ucat/topic-performances?timing=0Accept: application/json
  3. Auth probe for check_connection = mock-scores-stats, not HTML routes.
  4. Cookie jar may authenticate without env vars; keep that behaviour.

Adding or changing a tool

  1. Implement pure analysis in src/analysis/ when possible (unit-testable).
  2. Add fetch helpers on MedifyScoreService in endpoints.ts if new HTTP is needed.
  3. Add Tool schema + handler in src/tools/.
  4. Register in src/index.ts (TOOLS + switch).
  5. Bump package.json version; keep server version in index.ts aligned.
  6. 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)
  7. Update root README.md tools table if the public surface changed.
  8. npm test && npm run build.

Analysis modules

Read the full file on GitHub · 65 lines

Changes

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.

  1. 4d ago First seen · 65 lines · 53 tokens per session scan A 4b00e2bfeebc

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 tokens

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…

openai/codex · 113 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens