Install
$ agentstack add skill-msiccdev-ai-context-kit-repository-drift-control ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Repository Drift Control
Purpose
Prevent divergence between authoritative specification, operational prompts/templates, and repository-facing documentation.
When To Use
- Use this skill when specification or governance files change.
- Use this skill during repo-wide refactors affecting canonical paths or precedence rules.
- Do not use this skill for isolated content edits without cross-artifact impact.
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/repository-drift-control/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See [Invoking Skills](../../README.md#invoking-skills) in the README for full platform guidance.
Required Inputs
- Changed authoritative artifact(s), especially
specs/context_aware_ai_session_spec.md. - Current canonical path map.
- List of dependent files expected to be audited.
Workflow
- Identify source-of-truth changes and affected dependency set.
- Audit templates, prompts, samples, README, and AGENTS for alignment.
- Apply consistent terminology and path references.
- Verify policy and precedence remain coherent after updates.
- Record drift-control outcomes in commit/PR summary.
Output Expectations
- Aligned artifacts with no stale references.
- Stable canonical paths and precedence documentation.
- Clear audit trail of what was updated and why.
Resources
- Governance contract:
../../AGENTS.md - Repository guide:
../../README.md - Authoritative model:
../../specs/context_aware_ai_session_spec.md
Constraints And Safety
- Treat specification as authoritative when conflicts exist.
- Keep guidance provider-neutral.
- Preserve canonical path stability unless explicitly migrating.
- Avoid partial updates that leave dependent artifacts inconsistent.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MSiccDev
- Source: MSiccDev/ai-context-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.