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.
git clone --depth 1 https://github.com/Sagargupta16/claude-skillsWrote 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/sagargupta16/claude-skills/context-advisor)<a href="https://agentmods.dev/agents/sagargupta16/claude-skills/context-advisor"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/context-advisor.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.00076 | $0.00280 |
| Opus 5 | $0.00038 | $0.00140 |
| Sonnet 5 | $0.00015 | $0.00056 |
| Haiku 4.5 | $0.00008 | $0.00028 |
Grade A, and why
context-advisor 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 8d 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.
What it actually says
Context Health Advisor
Process
- Estimate context usage based on conversation length and complexity
- Look for symptoms of context rot:
- Repeated mistakes or ignored corrections
- Generic output that doesn't match project conventions
- Instructions from CLAUDE.md being forgotten
- Assess the current task state:
- Is work in progress that needs context preserved?
- Are there failed approaches polluting the context?
- Is the task nearly complete or just starting?
- Recommend the best action with specific reasoning
Output Format
## Context Health Assessment
**Estimated usage**: [low/medium/high/critical]
**Symptoms**: [list any context rot symptoms observed]
**Recommendation**: [Continue / Compact / Clear / New Session]
**Reason**: [why this action]
**Instructions**: [specific steps to take]
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.
- 8d ago First seen · 34 lines · 76 tokens per session scan A 5489e387971e
context-advisor is an agent published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 280 once invoked, about $0.0004 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 agents, from other repositories
workflow-orchestrator
Coordinates development workflows and orchestrates base plugin operations including git workflows, quality checks, and productivity automation.
search-plus
Enhanced web search and content extraction with intelligent multi-service fallback strategy for reliable access to blocked or problematic domains.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.
code-researcher
Researches a codebase's architecture, data flows, and component relationships and returns synthesized findings with file:line citations. Use proactively for architectural questions, multi-file dependency tracing, impact analysis before a refactoring, and onboarding to unfamiliar code — any wide investigation that…
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…