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 pjt222/agent-almanac --skill decommission-validated-systemgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/decommission-validated-system)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/decommission-validated-system"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/decommission-validated-system/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/pjt222/agent-almanac/decommission-validated-system"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/decommission-validated-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.02329 |
| Opus 5 | $0.00042 | $0.01164 |
| Sonnet 5 | $0.00017 | $0.00466 |
| Haiku 4.5 | $0.00008 | $0.00233 |
Grade A, and why
decommission-validated-system 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 5d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decommission Validated System
Plan and execute the controlled retirement of a validated computerized system while preserving data integrity and meeting regulatory retention requirements.
When to Use
- A validated system is being replaced by a new system
- A system is reaching end-of-life with no replacement (business process eliminated)
- Vendor discontinues support for a validated product
- Consolidation of multiple systems into a single platform
- Regulatory or business changes render a system obsolete
Inputs
- Required: System to be decommissioned (name, version, validation status)
- Required: Data retention requirements by regulation (21 CFR Part 11, GLP, GCP)
- Required: Replacement system (if applicable) and migration scope
- Optional: Current validation documentation package
- Optional: Data volume and format inventory
- Optional: Business owner and stakeholder list
Procedure
Step 1: Assess Data Retention Requirements
Determine how long data must be retained and in what form:
# Data Retention Assessment
## Document ID: DRA-[SYS]-[YYYY]-[NNN]
### Regulatory Retention Requirements
| Regulation | Data Type | Retention Period | Format Requirements |
|-----------|-----------|-----------------|-------------------|
| 21 CFR 211 (GMP) | Batch records, test results | 1 year past product expiry or 3 years after distribution | Readable, retrievable |
| 21 CFR 58 (GLP) | Study data and records | Duration of study + retention agreement | Original or certified copy |
| ICH E6 (GCP) | Clinical trial records | 2 years after last marketing approval or formal discontinuation | Accessible for inspection |
| 21 CFR Part 11 | Electronic records | Per predicate rule | Original format or validated migration |
| EU Annex 11 | Computerized system records | Per applicable GxP | Readable and available |
| Tax/financial | Financial records | 7-10 years (jurisdiction-dependent) | Readable |
### System Data Inventory
| Data Category | Volume | Format | Retention Required Until | Disposition |
|---------------|--------|--------|------------------------|-------------|
| [e.g., Batch records] | [e.g., 50,000 records] | [e.g., Database + PDF reports] | [Date] | Migrate / Archive / Destroy |
| [e.g., Audit trail] | [e.g., 2M entries] | [e.g., Database] | [Same as parent records] | Archive |
| [e.g., User data] | [e.g., 200 profiles] | [e.g., LDAP/Database] | [Employment + 2 years] | Anonymise and archive |
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.
- 5d ago First seen · 217 lines · 83 tokens per session scan A a864f4f08fab
decommission-validated-system is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 2,329 once invoked, about $0.0004 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-03.
Other skills, from other repositories
crisis-holding
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
cocoaudit
View and export the append-only session audit trail for regulated environments.
audit-add
Add a clearly marked manual CocoAudit event. Usage: $audit add " ".
audit-timeline
Render CocoAudit records as a compact chronological timeline. Usage: $audit timeline.
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
audit-ci
V2-native deterministic contract for the owning CocoPlus feature. Executes the behavior formerly delegated to audit-ci skill without registered runtime scripts.