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 remediategit 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/remediate)<a href="https://agentmods.dev/skills/prajapatimehul/comp-agent/remediate"><img src="https://agentmods.dev/badge/skills/prajapatimehul/comp-agent/remediate/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/prajapatimehul/comp-agent/remediate"><img src="https://agentmods.dev/badge/skills/prajapatimehul/comp-agent/remediate.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.00014 | $0.00460 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
remediate 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 9d 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
/remediate
Fix open compliance findings identified by the scanner.
Instructions
Single Finding
If $ARGUMENTS contains a specific finding ID (e.g., FINDING-s3-a1b2c3d4):
Use the Agent tool to spawn a single remediator agent:
subagent_type:remediator- Pass the finding ID in the prompt
All Open Findings
If $ARGUMENTS is all or empty:
- Read all finding files from
.compliance/findings/FINDING-*.json - Filter to findings where
statusisopen - Optionally filter by
--severityif provided in arguments - Sort by severity (critical first, then high, medium, low)
- For each open finding, spawn a remediator agent using the Agent tool:
subagent_type:remediator- Pass the finding file path in the prompt
- Run remediators in parallel where possible (up to 3 concurrent)
Severity Filter
If $ARGUMENTS contains --severity critical,high:
- Only remediate findings matching those severity levels
Usage Examples
/remediate # Remediate all open findings
/remediate FINDING-s3-a1b2c3d4 # Fix one specific finding
/remediate all # Same as no args
/remediate --severity critical # Only critical findings
/remediate --severity critical,high # Critical and high
Output
For each finding, the remediator will:
- Show the proposed fix and wait for approval
- Capture before/after evidence
- Apply the fix
- Verify with a Prowler re-check
- Update the finding status
After all remediations, show a summary of what was fixed.
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.
- 9d ago First seen · 57 lines · 14 tokens per session scan A 57e227f5e314
remediate is a skill published in the GitHub repository prajapatimehul/comp-agent (5 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 460 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.
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…
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.
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…