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 skills/msiccdev/ai-context-kit/create-usercontext-instructionsnpx skills add MSiccDev/ai-context-kit --skill create-usercontext-instructionsgit clone --depth 1 https://github.com/MSiccDev/ai-context-kitWhat 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 | $0.00022 | $0.00567 |
| Opus 5 | $0.00011 | $0.00283 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
create-usercontext-instructions 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create User Context Instructions
Purpose
Generate a complete user-context instruction file with required sections, privacy-aware content handling, and consistent output formatting.
When To Use
- Use this skill when the task is to create or regenerate a
*_usercontext.instructions.mdfile. - Use this skill when user context must be gathered through structured phases.
- Do not use this skill for project
AGENTS.md(project context) files.
How to Invoke
Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/create-usercontext-instructions/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.
Required Inputs
- Target identity label and role/title.
- Privacy expectations (full detail vs placeholders).
- Technical profile, projects, goals, style, and constraints.
- Desired output filename/path.
Workflow
- Run phased discovery using
references/discovery-phases.md. - Normalize findings into required schema using
references/output-schema.md. - Apply format contract from
references/output-format.md. - Stamp
spec_version: "1.4.3"in the YAML frontmatter of the generated artifact. - Validate against
references/quality-checklist.mdbefore final output. - If structured metadata is requested, apply
references/json-metadata-schema.md.
Output Expectations
- One complete
*.instructions.mdfile for user context. - Required section coverage and logical ordering are preserved.
- Privacy handling is explicit and consistent.
- Output is provider-neutral.
- Output contract and summary format follow
references/output-format.md.
Resources
- Discovery workflow:
references/discovery-phases.md - Output schema:
references/output-schema.md - Optional metadata schema:
references/json-metadata-schema.md - Output contract:
references/output-format.md - Quality checklist:
references/quality-checklist.md - Structure baseline:
../../templates/usercontext_template.instructions.md - Example reference:
../../usercontexts/sample_usercontext.instructions.md
What ships with it
6 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.
- 2d ago First seen · 60 lines · 22 tokens per session scan A 4816f1219011
create-usercontext-instructions is a skill published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 567 once invoked, about $0.0001 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-30.
Other skills, from other repositories
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
explain
Learn why structured context matters. Quick explanation for skeptics and the curious.
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
apm-usage
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.
kayba-pipeline
End-to-end agent evaluation and improvement pipeline. Takes a traces folder and optional HITL flag, then orchestrates sub-agents through 7 stages — each stage is its own skill invoked by a dedicated sub-agent. Trigger when the user says "run the pipeline", "kayba pipeline", "evaluate and fix", "full eval", "analyze…