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/validate-project-instructionsnpx skills add MSiccDev/ai-context-kit --skill validate-project-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.00028 | $0.00535 |
| Opus 5 | $0.00014 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
validate-project-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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Project Context AGENTS
Purpose
Validate project-context AGENTS.md files with structured checks for required sections, session-state controls, role definitions, and core required-section completeness based on a deterministic scoring rubric.
When To Use
- Use this skill to validate project-context
AGENTS.mdfiles. - Use this skill when reviewing project context quality prior to active use.
- Do not use this skill for user-context instruction validation.
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/validate-project-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 project-context
AGENTS.mdpath. - Expected section model and command reference expectations.
- Any strictness preferences for warnings vs required fixes.
Workflow
- Run validation phases from
references/phase-checks.md. - Check for
<!-- spec_version: ... -->comment: flag as WARNING if absent (pre-existing files may predate this requirement); flag as WARNING if present but older than1.4.3. - Generate report using
references/report-contract.md. - Apply deterministic scoring from
references/scoring.md. - Classify findings into critical/warning/enhancement buckets.
- Produce project-specific remediation guidance.
Output Expectations
- Structured markdown report with five validation phases.
- Clear status for critical issues vs warnings.
- Numeric score and grading band.
- Concrete example fixes for major gaps.
- Report schema follows
references/report-contract.md. - Scoring and grade bands follow
references/scoring.md.
Resources
- Phase checks:
references/phase-checks.md - Report contract:
references/report-contract.md - Scoring model:
references/scoring.md - Example target:
../../AGENTS.md
What ships with it
4 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 · 57 lines · 28 tokens per session scan A 595758a3fd5c
validate-project-instructions is a skill published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 535 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.
init
Initialize structured context for this project. Scaffolds .scs/ with all 11 concern bundles, scans the project, and recommends where to start.
add
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync status.
validate
Check structure and surface issues for human review. Validates YAML, references, concern coverage, and compilation 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.