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 Azzygoatcoder/agent-useful-skills --skill security-fix-skillgit clone --depth 1 https://github.com/Azzygoatcoder/agent-useful-skillsWrote 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/azzygoatcoder/agent-useful-skills/security-fix-skill)<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/security-fix-skill"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/security-fix-skill/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/azzygoatcoder/agent-useful-skills/security-fix-skill"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/security-fix-skill.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.00104 | $0.01106 |
| Opus 5 | $0.00052 | $0.00553 |
| Sonnet 5 | $0.00021 | $0.00221 |
| Haiku 4.5 | $0.00010 | $0.00111 |
Grade A, and why
security-fix-skill 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security fix workflow
This skill guides the systematic remediation of security audit findings, grouped by priority level (P1–P4). The process was refined across 16 real-world findings in a Python web application project.
Step 1: Load the audit report
Read the audit document (typically docs/SECURITY_AUDIT.md). Extract:
- Each finding's ID, severity, affected file, line number, and description
- The remediation code or instructions provided
- The priority rating (P1 = fix immediately, P4 = address when convenient)
Present a summary table to the user showing severity distribution and file-level impact, then ask which priority level to start with.
Step 2: Fix one priority level at a time
For each finding in the current priority:
- Read the affected code at the specified file and line range
- Apply the remediation from the audit doc — prefer minimal, targeted edits that don't change behavior
- Verify the fix by re-reading the changed lines
- Track progress: "3 of 5 P1 fixes applied"
Step 3: Test after each priority level
After completing all fixes at a priority level:
pytest tests/ -x -q # or the project's test command
If any tests fail, investigate before proceeding. The most common failure mode is monkeypatch targets changing when code moves between modules.
Step 4: Commit the batch
Commit all fixes at the current priority level together:
git add -u
git commit -m "fix: security — <summary> (P<N> SSRF-1 PATH-1 AUTH-1)"
Use conventional commit format. Include the finding IDs in the commit message body so they are traceable. Push when requested by the user.
Step 5: Mark-fixed and move to next priority
After committing each priority batch:
- Run
/reaudit mark-fixed <ID>for each finding in the batch. This updates the report's status annotations without re-reading files. - Repeat steps 2–5 for the next priority level. Typical execution order: P1 (5 findings, ~15 min) → P2 (4 findings, ~10 min) → P3 (3 findings, ~10 min) → P4 (4 findings, ~10 min)
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 · 117 lines · 104 tokens per session scan A 35fcf7003e8b
security-fix-skill is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (6 stars, last pushed 10d ago), licensed MIT. It adds 104 tokens to every session and 1,106 once invoked, about $0.0005 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
dsh-plugin-dev
An authoritative development guide for DeepSeek Harness plugins. DeepSeek Harness is a system where models, tools, services, events, and adapters are built as plugins.
dsh-plugin-client
A development guide for the browser interface of a DSH plugin, including its package structure, registered interface locations, and build setup.
dsh-plugin-dev
A guide for creating and debugging DeepSeek Harness plugins, which are add-ons packaged as npm modules with configuration files.
dsh-plugin-i18n
A pattern for giving a DSH plugin’s user interface English and Chinese text that changes immediately when the selected language changes.
dsh-git-commit
A Git commit guide for writing standardised commit messages and performing basic checks before committing code. Git commits are saved checkpoints in a project’s history.
dsh-dependency-audit
A guide for reviewing and upgrading project dependencies, which are third-party packages the project relies on. It covers security warnings, installation scripts, lock files, breaking changes, tests, rollback plans, and reducing unnecessary dependencies.