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 joao-aires/agent-skills-public --skill soc2-readinessgit clone --depth 1 https://github.com/joao-aires/agent-skills-publicWrote 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/joao-aires/agent-skills-public/soc2-readiness)<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/soc2-readiness"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/soc2-readiness/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/joao-aires/agent-skills-public/soc2-readiness"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/soc2-readiness.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.00044 | $0.00704 |
| Opus 5.5 | $0.00018 | $0.00282 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
soc2-readiness 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 yesterday.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess the service and its control evidence
Establish why the report is needed, the actual service/customer commitments, intended report type/timeframe and available auditor/scoping decisions. Reuse existing controls and evidence. SOC 2 is an assurance examination of scoped controls, not a regulation or a property created by a passing application test. Read control and evidence reasoning and the official source guide when scoping or mapping criteria.
Define the relevant boundary
Describe the service, people/processes, software, infrastructure, data, vendors and customer responsibilities.
- Distinguish in-scope service commitments and system requirements from unaccepted future features.
- Establish relevant Trust Services categories and description requirements with the responsible assurance owner/auditor; do not require every category simply because it exists.
Identify dependencies and the selected treatment of subservice organizations and complementary controls. A cloud provider's report can support a dependency assessment but does not cover all application controls or the customer's responsibilities. Architecture and access/operating boundaries should agree with the described service.
Connect criteria to operating controls
For each relevant criterion or service commitment, identify the process that is intended to satisfy it. Explain the action, responsible owner, trigger or frequency, and the population of events to which it applies. Then identify the source that can show whether those events were handled as intended.
Evaluate the process and its evidence together. An automated job needs evidence of its relevant runs and how failures were handled; a performed review needs evidence of what was reviewed and how exceptions were resolved. These are evidence questions to settle with the responsible assurance owner, not a requirement to adopt a particular document or platform. Preserve the actual examination scope and period.
What ships with it
1 file 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.
- yesterday First seen · 55 lines · 44 tokens per session scan A 20406e7ed5bb
soc2-readiness is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 704 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
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.
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.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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.