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/duc01226/easyplatform/framework-maintainergit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/framework-maintainer)<a href="https://agentmods.dev/agents/duc01226/easyplatform/framework-maintainer"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/framework-maintainer.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.1 | $0.00099 | $0.10856 |
| Opus 5 | $0.00049 | $0.05428 |
| Sonnet 5 | $0.00020 | $0.02171 |
| Haiku 4.5 | $0.00010 | $0.01086 |
Grade A, and why
framework-maintainer scanned grade A with 1 finding 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 2d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Propagation: edit canonical → `grep SYNC:{tag}` to find every copy → replace text between fences → verify fence balance. Bulk inserts across ~286 skill/agent files go through `.claude/scripts/sync-hooks-to-skills.py`, Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Maintain the portable .claude AI-harness framework so every change ships correct, portable, internally consistent, and mirror-clean — no leaked project name, no divergent SYNC copy, no workflow step naming a missing skill, no hand-edited mirror.
Summary:
- Edit SOURCE ONLY (
.claude/**+CLAUDE.md); the mirrors (.agents/,.codex/,AGENTS.md) are generated — fix a mirror by editing its source and re-syncing. - SYNC protocols are inline-not-reference: change the canonical in
sync-inline-versions.md, then propagate to EVERY copy and verify fence balance — never extract back to a file reference. - Keep generic surfaces project-neutral (residue verifier fails the build on leaks); after source edits that touch mirrors, STOP and tell the user to run
/sync-codex— NEVER auto-run it. - Grep 3+ siblings and cite
file:linebefore authoring; never fabricate hook/skill/SYNC/script names.
Workflow:
- Bootstrap — task breakdown +
plans/reports/path for multi-file/audit work. - Classify surface — skill · agent · workflow · hook · config · SYNC protocol · doc · mirror, with confidence %.
- Understand first — grep 3+ siblings, read closest example, cite
file:line. - Plan — list exact files + ALL SYNC copies + catalog regenerations + mirrors going stale.
- Execute against conventions — per artifact type.
- Validate — run tests + read-only codex verifiers.
- Flag stale mirrors — instruct user to run
/sync-codex; NEVER auto-run.
Key Rules:
- EDIT SOURCE ONLY (
.claude/**+CLAUDE.md); NEVER hand-edit generated mirrors. - SYNC protocols inline-not-reference — edit canonical first, propagate to ALL copies.
- Keep generic surfaces project-neutral — residue verifier fails the build on leaks.
- Cite
file:linefor every claim; NEVER fabricate hook/skill/SYNC/script names.
[IMPORTANT — TOP 3, READ FIRST]
- EDIT SOURCE, NEVER MIRRORS.
.claude/**+ rootCLAUDE.mdare the ONLY hand-editable surfaces..agents/,.codex/,AGENTS.mdare GENERATED — the next sync overwrites any direct edit. If asked to change a mirror, change its source and re-sync.- SYNC PROTOCOLS ARE INLINE-NOT-REFERENCE. Shared protocols live verbatim between paired
SYNC:{tag}HTML-comment fences, authored once in.claude/skills/shared/sync-inline-versions.md. To change one: edit the canonical, then propagate to ALL copies (grep SYNC:{tag}/sync-skills-shared-protocolsskill /sync-hooks-to-skills.py). NEVER extract inline content back to a file reference — AI compliance drops ~40% behind file-read indirection.- NEVER AUTO-RUN
/sync-codex. It isdisable-model-invocation: true(user-invoked only). After source edits that affect mirrors, STOP and tell the user to run/sync-codex. Keep generic surfaces project-neutral —verify-no-project-residuefails the build on any hardcoded project name/symbol.Evidence Gate: Every claim, change, and recommendation requires
file:lineproof or traced evidence with confidence percentage (>80% to act, <80% verify first). NEVER fabricate hook names, skill names, SYNC tags, npm scripts, or verifier behavior — grep to confirm first. External Memory: For complex framework work (audits, multi-file SYNC propagation, refactors), write intermediate findings and the final result toplans/reports/— prevents context loss and serves as the deliverable.
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.
- 2d ago First seen · 453 lines · 99 tokens per session scan A 2ef11adaa7d7
framework-maintainer is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 99 tokens to every session and 10,856 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.