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 tahirraufkeeyu/software-development-agent-stack--sdas --skill compliance-remediationgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/compliance-remediation)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/compliance-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/compliance-remediation/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/tahirraufkeeyu/software-development-agent-stack--sdas/compliance-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/compliance-remediation.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.03942 |
| Opus 5 | $0.00037 | $0.01971 |
| Sonnet 5 | $0.00015 | $0.00788 |
| Haiku 4.5 | $0.00007 | $0.00394 |
Grade A, and why
compliance-remediation 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 11d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
compliance-checkhas producedsecurity/findings/compliance.jsonwith one or more gap findings.- A Drata / Vanta / Secureframe / Thoropass test has failed and requires engineering action.
- An auditor interim walkthrough surfaced control deficiencies that need closure before the audit period ends.
- A new framework is being adopted (e.g. moving from SOC2 Type I to Type II, or adding ISO 27001) and you need to close gaps surfaced by the readiness assessment.
Do not use this skill to perform the audit itself — that's compliance-check. Do not use it for CVE closure — that's dependency-remediation or vulnerability-remediation.
Inputs
security/findings/compliance.jsonwith control IDs, gap classification, and evidence.- The framework's control register (Trust Service Criteria for SOC2, Annex A for ISO 27001, etc.).
- Write access to the policy repo (
policies/), config management (IAM, Okta, logging), and the evidence store. - Stakeholders mapped per control family (HR for CC1, Security for CC6, Eng for CC8, etc.).
Outputs
security/remediation/compliance-<framework>-<date>.md— per-gap remediation trail.- New or updated policy documents under
compliance/<framework>/<control-id>/policy.md. - Technical control configurations (IAM policies, SSO groups, monitoring rules, access-review reports).
- Evidence artifacts collected and stored under
compliance/<framework>/<control-id>/evidence/<date>-<artifact>.{pdf,json,png}. - Test-of-effectiveness documentation under
compliance/<framework>/<control-id>/tests.md.
Tool dependencies
- Cloud / SaaS CLIs:
aws,gcloud,okta-awscli,gh,tsc(Drata), or Vanta / Secureframe APIs. git(policy docs in version control).- An evidence locker — S3 with Object Lock, Google Drive with restricted sharing, or a GRC platform's evidence module.
- A diagramming tool (Mermaid / draw.io) for policy flowcharts.
Procedure
- Classify each gap into one of three types. This determines the remediation path.
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.
- 11d ago First seen · 374 lines · 75 tokens per session scan A d90001654329
compliance-remediation is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 3,942 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-08-30.
Other skills, from other repositories
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…