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 full-security-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/full-security-remediation)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/full-security-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/full-security-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/full-security-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/full-security-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.00086 | $0.03377 |
| Opus 5 | $0.00043 | $0.01688 |
| Sonnet 5 | $0.00017 | $0.00675 |
| Haiku 4.5 | $0.00009 | $0.00338 |
Grade A, and why
full-security-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 10d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- You have run
full-security-auditand all 5 findings JSONs exist undersecurity/findings/. - A release is gated on closing High+ findings across multiple classes and you want a single orchestrated cycle rather than running each remediation skill manually.
- An incident response has mandated a full security sweep + closure within a fixed deadline.
- Pre-audit readiness: an external pen-test or SOC2 observation window starts soon and you need a consolidated before/after report.
Do not use this skill to run the audit itself — that's full-security-audit. Do not use it when only one class of finding exists — invoke the specific remediation skill directly.
Chained skills
secret-remediation— rotates leaked credentials, rewrites git history, installs prevention controls. Always runs FIRST if any secret findings exist.dependency-remediation— upgrades / overrides / replaces vulnerable packages, commits lockfile changes, re-runs audit.vulnerability-remediation— fixes SAST/DAST findings in code and config with regression tests per finding.container-remediation— rebases container images, hardens Dockerfiles, rebuilds clean, re-scans with Trivy. Runs only if a Dockerfile exists in the repo.compliance-remediation— closes SOC2/ISO control gaps with policy, technical control, and evidence artifacts.
Inputs
security/findings/secrets.jsonsecurity/findings/dependencies.jsonsecurity/findings/audit.jsonsecurity/findings/container.json(optional — skipped if missing)security/findings/compliance.json
The orchestrator expects all required JSONs to exist. A missing non-optional input is an error — re-run full-security-audit first.
Outputs
security/remediation/full-remediation-<date>.md— consolidated remediation report.- Individual remediation reports linked:
secrets-<date>.md,dependencies-<date>.md,vulnerabilities-<date>.md,container-<image>-<date>.md,compliance-<framework>-<date>.md. - A release-gate verdict: PASS (no HIGH+ residuals without approved exception) or FAIL.
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.
- 10d ago First seen · 230 lines · 86 tokens per session scan A ab95e59ba233
full-security-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 86 tokens to every session and 3,377 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…