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 skills add LIXianSenQwQ/classmap-skill --skill classmap-maintaingit clone --depth 1 https://github.com/LIXianSenQwQ/classmap-skillWrote 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/lixiansenqwq/classmap-skill/classmap-maintain)<a href="https://agentmods.dev/skills/lixiansenqwq/classmap-skill/classmap-maintain"><img src="https://agentmods.dev/badge/skills/lixiansenqwq/classmap-skill/classmap-maintain/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/skills/lixiansenqwq/classmap-skill/classmap-maintain"><img src="https://agentmods.dev/badge/skills/lixiansenqwq/classmap-skill/classmap-maintain.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.00062 | $0.00901 |
| Opus 5.5 | $0.00025 | $0.00360 |
| Sonnet 5.5 | $0.00012 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
classmap-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 14d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
classmap-maintain
Maintain CLASSMAP.md so an agent can answer: "Which code should I inspect for this behavior, and where does its responsibility end?"
Keep it a small, human-readable index of useful entrypoints and responsibilities.
Scope
- A request limited to inspection, explanation, or drift checking is read-only. Report discrepancies without editing the map.
- A request to create, refresh, or repair the map authorizes maintenance within that scope. A bare invocation uses the default create-or-refresh task.
- A missing or stale map alone does not authorize creating or updating it during another task.
- Prefer code evidence over asking the user. Ask only when an important ambiguity cannot be resolved from code and relevant docs.
- Trust current code when it conflicts with the map. Do not implement business features as part of map maintenance.
Workflow
- Confirm the project and requested scope. Read the existing
CLASSMAP.mdand inspect the relevant source/module structure. ConsultREADME.md,CODEMAP.md,CONTEXT.md, or specific docs only where they help identify entrypoints; do not read all documentation by default. - Start from the main behaviors in scope and follow their entrypoints into the responsible code. Ignore generated, vendor, dependency, and build output.
- Verify paths and responsibilities in code. Use existing docs as navigation clues. Describe specific uncertainty when a responsibility cannot be confirmed; do not guess or assign confidence scores.
- For inspection, report the verified findings. For maintenance, make targeted edits, preserving useful manual notes and existing layout unless they contradict code. Do not convert a useful existing map solely to match the example below.
- For a first map, stop when the identified main behaviors have reliable entrypoints and important boundaries are clear. Briefly note uncovered areas if coverage is partial; exhaustive file coverage is unnecessary. For an existing map, stop when the requested scope is checked or updated.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · -76 lines · -24 tokens per session 13d86182bcb8
- 2mo ago First seen · 139 lines · 86 tokens per session scan A 556b99530038
classmap-maintain is a skill published in the GitHub repository LIXianSenQwQ/classmap-skill (5 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 901 once invoked, about $0.0002 per session on Opus 5.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
context-exclusion
Maintain .agent-no-read.md markers for approved generated directories using deterministic scripts. Use when configuring generated-code context exclusion or restoring markers after regeneration, not for ordinary ignore rules or OS permissions.
context-engineering
A project documentation framework that records a project's goals, requirements, roadmap, and current state in separate files. It also keeps those documents within set size limits for an AI coding agent.
error-experience-library
An error knowledge base that stores recurring error patterns, their causes, and the fixes that worked. It can search past entries and track whether each suggested fix succeeded.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
chronicle-skysight
Use when recent Linux desktop activity memory would help answer a question or when the user asks to inspect or control Chronicle or Skysight.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…