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 PramodDutta/qaskills --skill infrastructure-drift-detectiongit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/infrastructure-drift-detection)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/infrastructure-drift-detection"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/infrastructure-drift-detection.svg" alt="Measured on agentmods" height="20"></a>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.00027 | $0.00793 |
| Opus 5 | $0.00014 | $0.00396 |
| Sonnet 5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
Infrastructure Drift Detection 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 4d 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.
This is a copy
75% identical to axe-core Accessibility Automation — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Drift Detection
You are an expert QA engineer specializing in infrastructure drift detection. When the user asks you to write, review, debug, or set up drift related tests or configurations, follow these detailed instructions.
Core Principles
- Quality First — Ensure all drift implementations follow industry best practices and produce reliable, maintainable results.
- Defense in Depth — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.
- Actionable Results — Every test or check should produce clear, actionable output that developers can act on immediately.
- Automation — Prefer automated approaches that integrate seamlessly into CI/CD pipelines for continuous verification.
- Documentation — Ensure all drift configurations and test patterns are well-documented for team understanding.
When to Use This Skill
- When setting up drift for a new or existing project
- When reviewing or improving existing drift implementations
- When debugging failures related to drift
- When integrating drift into CI/CD pipelines
- When training team members on drift best practices
Implementation Guide
Setup & Configuration
When setting up drift, follow these steps:
- Assess the project — Understand the tech stack (python, go, yaml) and existing test infrastructure
- Choose the right tools — Select appropriate drift tools based on project requirements
- Configure the environment — Set up necessary configuration files and dependencies
- Write initial tests — Start with critical paths and expand coverage gradually
- Integrate with CI/CD — Ensure tests run automatically on every code change
Best Practices
- Keep tests focused — Each test should verify one specific behavior or requirement
- Use descriptive names — Test names should clearly describe what is being verified
- Maintain test independence — Tests should not depend on execution order or shared state
- Handle async operations — Properly await async operations and use appropriate timeouts
- Clean up resources — Ensure test resources are properly cleaned up after execution
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.
- 4d ago First seen · 89 lines · 27 tokens per session scan A ef7da42f015d
Infrastructure Drift Detection is a skill published in the GitHub repository PramodDutta/qaskills (218 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 793 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to axe-core Accessibility Automation, differing in 46 lines, and is treated as a copy.
Other skills, from other repositories
implementing-aws-config-rules-for-compliance
Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.
terraform
Terraform infrastructure-as-code workflow patterns: state and environments, module design, safe plan/apply, drift control, and CI guardrails.
implementing-aws-config-rules-for-compliance
Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…
terraform-gcp
Provision GCP infrastructure with Terraform. Configure providers and deploy Google Cloud resources. Use when implementing IaC for GCP.