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 prajapatimehul/comp-agent --skill posturegit clone --depth 1 https://github.com/prajapatimehul/comp-agentWrote 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/prajapatimehul/comp-agent/posture)<a href="https://agentmods.dev/skills/prajapatimehul/comp-agent/posture"><img src="https://agentmods.dev/badge/skills/prajapatimehul/comp-agent/posture.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.00010 | $0.00589 |
| Opus 5 | $0.00005 | $0.00295 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
posture 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 8d 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.
What it actually says
/posture
Show a quick compliance posture summary. Read-only — does not spawn subagents.
Instructions
Do NOT use the Agent tool. Handle this directly.
1. Read All Findings
Use Glob to find all .compliance/findings/FINDING-*.json files, then Read each one.
If no findings exist, report:
No findings found. Run /scan first to assess your AWS account.
2. Compute Statistics
Count findings by:
- Status: open, in_progress, remediated, verified, skipped
- Severity: critical, high, medium, low
- Service: group by
source.service - Framework: group by
compliance[].framework
Calculate compliance percentage:
compliance% = (verified + skipped) / total * 100
3. Display Summary
# Compliance Posture
Last scan: {most recent scanId from findings}
Total findings: {n}
## By Status
| Status | Count |
|--------|-------|
| Open | {n} |
| In Progress | {n} |
| Remediated | {n} |
| Verified | {n} |
| Skipped | {n} |
## By Severity
| Severity | Open | Fixed | Total |
|----------|------|-------|-------|
| Critical | {n} | {n} | {n} |
| High | {n} | {n} | {n} |
| Medium | {n} | {n} | {n} |
| Low | {n} | {n} | {n} |
## By Framework
| Framework | Controls Hit | Findings | Verified | Score |
|-----------|-------------|----------|----------|-------|
| SOC 2 | {n unique controls} | {n} | {n} | {%} |
| HIPAA | {n unique controls} | {n} | {n} | {%} |
## By Service
| Service | Open | Fixed | Total |
|---------|------|-------|-------|
| s3 | {n} | {n} | {n} |
| iam | {n} | {n} | {n} |
| ... | ... | ... | ... |
## Top Open Issues
{List top 5 open findings by severity, with finding ID, check title, and resource}
4. Framework Filter
If $ARGUMENTS contains --framework soc2 or --framework hipaa:
- Only show findings mapped to that framework
- Adjust all counts accordingly
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.
- 8d ago First seen · 85 lines · 10 tokens per session scan A f9aa0841c42f
posture is a skill published in the GitHub repository prajapatimehul/comp-agent (5 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 589 once invoked, about $0.0001 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-31.
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…