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 ALTEN-group/coding-pal --skill context-healthgit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/context-health)<a href="https://agentmods.dev/skills/alten-group/coding-pal/context-health"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/context-health/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/alten-group/coding-pal/context-health"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/context-health.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.00085 | $0.00604 |
| Opus 5.5 | $0.00034 | $0.00242 |
| Sonnet 5.5 | $0.00017 | $0.00121 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
context-health 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Health
Keep Persistent Context small, specific, scoped, current, and secret-free, and let evidence decide what to add: a topic corrected or re-explained twice becomes a proposed artifact.
When to Use This Skill
- The weekly Persistent Context & Controls review needs its pack.
- An instruction file was added or changed and CI should lint it.
- A reviewer corrected or re-explained the same thing again and it should be logged.
- Someone asks whether the instruction set is growing without pruning.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/context-health/ or .claude/skills/context-health/, use that base path.
Workflow
- Read
references/context-health-contract.mdnow. It lists the rules, severities, the baseline format, and the log format. - Lint the consumer repository from this skill's directory:
node scripts/context-lint.mjs --root . --baseline context-baseline.json
Fix errors (missing description, dangling references, secrets). Rotate a reported secret, do not only delete it. Report warnings (long, duplicate, stale, growth) for the Architect to decide.
- Log a correction or re-explanation as soon as it happens:
node scripts/context-corrections.mjs add --log specs/learn/corrections.jsonl \
--topic "Use named exports" --source "PR #123"
- Before the review, list the topics that earned an artifact:
node scripts/context-corrections.mjs propose --log specs/learn/corrections.jsonl --min 2
- Add control signal-to-noise findings only as the user supplies them (how often a control fires and is bypassed). Never invent numbers.
--write-baselineis a human decision made in a pull request, not something to run to silence the growth warning.
Done When
context-lint.mjsexits 0 (no errors) on the repository.- Every proposal comes from the corrections log, and each is presented as a proposal for the Architect.
- No file was changed to hide a finding: no rewritten baseline, no deleted log line.
What ships with it
5 files 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.
- 3d ago First seen · 54 lines · 85 tokens per session scan A bfaf0cde5d9e
context-health is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 604 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.