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/skill_templatenpx skills add MSiccDev/ai-context-kit --skill skill_templategit 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.00018 | $0.00459 |
| Opus 5 | $0.00009 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
example-skill 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 yesterday.
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
Example Skill
Purpose
Describe the capability this skill provides and the problem it solves.
When To Use
- Use this skill when the task matches this domain.
- Do not use this skill for unrelated tasks.
Required Inputs
- List required information the assistant needs before applying this skill.
Workflow
- Confirm the task fits the skill scope.
- Gather only the inputs required for this workflow.
- Execute steps in order and verify outputs.
Output Expectations
- Define the expected output format and quality criteria.
- Include any acceptance checks.
Resources
references/for detailed docs loaded on demand.scripts/for optional automation or checks.assets/for reusable static artifacts.
Constraints And Safety
- Keep instructions concise in this file; move large material to
references/. - Use relative paths for all skill-local references.
- Mention risky operations explicitly and require confirmation before running them.
Frontmatter Rules
name(required):- 1-64 characters.
- Lowercase letters, numbers, and hyphens only.
- No leading/trailing hyphen.
- No consecutive hyphens.
- Must match the parent skill directory name.
description(required):- 1-1024 characters.
- Must state what the skill does and when to use it.
license(optional): short license identifier.compatibility(optional):- 1-500 characters.
- Use only for real environment constraints.
metadata(optional): map of string keys to string values.version(optional): semver string (e.g."1.0.0"). Increment when skill behavior changes.allowed-tools(optional): YAML flow list of tool names this skill may invoke (e.g.[Read, Write, Edit]).
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.
- yesterday First seen · 61 lines · 18 tokens per session scan A d36c79769685
example-skill is a skill published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 459 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.
add
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
init
Initialize structured context for this project. Scaffolds .scs/ with all 11 concern bundles, scans the project, and recommends where to start.
validate
Check structure and surface issues for human review. Validates YAML, references, concern coverage, and compilation status.
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync status.
use
Add known compliance or regulatory standards (HIPAA, SOC2, PCI, CHAI, GDPR) to your project context. Copies pre-built standards SCDs from the plugin's standards library.