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 ai-analyst-lab/ai-analyst --skill improve-contextgit clone --depth 1 https://github.com/ai-analyst-lab/ai-analystWrote 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/ai-analyst-lab/ai-analyst/improve-context)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/improve-context"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/improve-context/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/ai-analyst-lab/ai-analyst/improve-context"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/improve-context.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.00065 | $0.00572 |
| Opus 5 | $0.00032 | $0.00286 |
| Sonnet 5 | $0.00013 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
improve-context 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 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve context
Use the evaluation system as the referee. Do not promote a context change because the new answer looks more plausible.
1. Diagnose
Read the failing evaluation record and its analysis trace. Classify the context failure:
- missing information;
- wrong information;
- stale information;
- conflicting information;
- correct information was not supplied;
- supplied information was ignored or misapplied;
- the problem belongs in a skill, helper, workflow, or evaluator rather than context.
Run /context-trace on the exact question. Preserve its JSON fingerprint.
2. Propose
Create working/context-change-proposal.yaml with:
- observed failure and evidence;
- smallest proposed change;
- representation and delivery;
- source and owner;
- status
proposed; - cases expected to improve;
- possible regressions;
- required reviewers;
- acceptance criteria.
Do not change trusted context until the user approves the proposal.
3. Preserve the baseline
Run the working and regression cases before the edit. Keep the manifest paths and run IDs. Freeze the suite, data snapshot, model, evaluator, and trial count.
Record the proposal's named target case IDs. For the Session 8 course fallback, use
data/evals/public/week4-context.yaml with the context-policy runner. Lock outputs before grading
against data/evals/working-references/week4-context.yaml.
4. Apply one change
Make only the approved context change. Show the diff. Do not change the evaluator or expected results in the same comparison.
5. Rerun and inspect
Run the same working and regression cases. Inspect:
- aggregate score;
- target cases;
- regressions;
- cases still failing;
- context manifest;
- context citations and SQL-use evidence.
6. Write the receipt
Use helpers.knowledge.context_change with the baseline and candidate manifests. Pass every named
target with --target-case, and verify that the actual changed system paths are a subset of the
approved changed paths. The receipt must recommend:
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 · 73 lines · 65 tokens per session scan A 6f7da4966d99
improve-context is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 572 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-09-12.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.