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 manishiitg/coding-agent-loop --skill application-security-assessment-remediationgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/application-security-assessment-remediation)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/application-security-assessment-remediation"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/application-security-assessment-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/manishiitg/coding-agent-loop/application-security-assessment-remediation"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/application-security-assessment-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.00046 | $0.00841 |
| Opus 5.5 | $0.00018 | $0.00336 |
| Sonnet 5.5 | $0.00009 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
application-security-assessment-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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Security Assessment and Remediation
Outcome
Create one governed AppSec workflow that inventories authorized attack surface, runs applicable assessment routes, validates findings, prepares fixes, obtains required decisions, and verifies remediation against the deployed result.
When to use
Use for authorized application assessment, CI security gates, bounded pentests, vulnerability intake, and remediation. Reuse verified Browser QA setup when applicable.
Discovery and user direction
Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers before proposing changes. Summarize reusable design and gaps, then ask focused questions for unresolved customer choices such as scope, success, approvals, thresholds, ownership, and budgets. Record the answers as customer direction. Installation alone does not approve workflow changes or execution. Default to one small-team workflow; split only for incompatible access or lifecycle boundaries.
Required inputs
Resolve written scope, targets/environments/repositories/APIs, rules of engagement, allowed techniques and side effects, credentials/test data, rate/time limits, stop conditions, control/severity policy, source and deployment identity, evidence restrictions, owners, approval/risk-acceptance policy, and retest/closure requirements.
Plan and AgentWorks tools
Use webhook/manual/Slack intake and a scripted scope gate. Route to browser/API dynamic checks, code analysis, or dependency/secret/configuration checks. Use scripted steps for repeatable tools, normalization, policy checks, fix validation, and retest; use a message sequence for attack-surface reasoning and evidence-based triage. Persist intrusive-test, remediation, risk-acceptance, and protected-change proposals as durable decisions, then use separate action routes to revalidate and execute approved work.
Knowledge and persistence
Store scopes, targets, runs, checks, observations, findings, evidence, decisions, fixes, deployments, retests, risk acceptances, and delivery receipts in durable tables/assets. Keep approved policies and non-sensitive verified facts in scoped KB notes. Keep exploit-sensitive details restricted.
What ships with it
10 files 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.
- examples/application-security-policy.json 980 B
- playbook.json 9.9 KB
- references/api-security-testing.md 3.0 KB
- references/assessment-routes.md 3.1 KB
- references/browser-security-testing.md 3.0 KB
- references/code-supply-chain-configuration.md 3.2 KB
- references/findings-remediation-verification.md 3.2 KB
- references/recommended-tools-and-skills.md 5.8 KB
- references/scope-and-authorization.md 3.3 KB
- references/triggers-slack-dashboard.md 3.6 KB
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.
- 1mo ago First seen · 54 lines · 46 tokens per session scan A 9cc38c07d2fc
application-security-assessment-remediation is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 841 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-09-14.
Other skills, from other repositories
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.
node-inspect-debugger
See runtime state a console.log cannot reach — set real breakpoints, step, and dump the scope chain of a paused Node/TypeScript process. Use on "set a breakpoint", "inspect runtime state", "console.log isn't enough", "step through this", "what's in this closure at runtime", "attach a debugger". Not a logging or…
browser
Browser automation via the agent-browser CLI. Use when the user needs to drive websites or Electron apps — navigating, forms, clicks, screenshots, data extraction, testing web apps, UI checks, the dashboard Electron shell, or the user's own logged-in Chrome via the browser relay or Panerelay (SSO/2FA). Triggers: "open…
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.