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 agentmods add skills/shipwithai/shipwithai-plugins/security-filter-chainnpx skills add ShipWithAI/shipwithai-plugins --skill security-filter-chaingit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/security-filter-chain)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/security-filter-chain"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/security-filter-chain.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.00095 | $0.00864 |
| Opus 5 | $0.00048 | $0.00432 |
| Sonnet 5 | $0.00019 | $0.00173 |
| Haiku 4.5 | $0.00010 | $0.00086 |
Grade A, and why
security-filter-chain 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Filter Chain — Scaffold
Generates a SecurityConfig whose authorization is deny-by-default, so a new
endpoint is locked until you explicitly open it — the opposite of the permit-all
defaults that trip sec-missing-method-auth. See references/security.md for the why.
Step 1 — Detect conventions (do not assume)
Read before generating:
- Existing security config: search for a
@Bean SecurityFilterChainor the legacyWebSecurityConfigurerAdapter. If one exists, EDIT it (show a diff) — two filter chains with overlapping matchers is non-deterministic. If it's the deprecated adapter, offer to migrate it to the component-basedSecurityFilterChainbean. - Auth model — pick before generating:
- Cookie/session (server renders, browser holds a session cookie) → KEEP CSRF,
allow the default
SessionCreationPolicy. - Stateless token (JWT/opaque bearer, no cookie) →
SessionCreationPolicy.STATELESSand CSRF disabled (no cookie to forge). Pair with thejwt-authskill.
- Cookie/session (server renders, browser holds a session cookie) → KEEP CSRF,
allow the default
- Origins: find the SPA/mobile origins for CORS; never reflect
*with credentials. - Base package: mirror existing
config/securitypackages.
Step 2 — Render the template
From assets/SecurityConfig.java.tmpl, substitute {{PACKAGE}} and {{ALLOWED_ORIGIN}}
→ <pkg>/config/SecurityConfig.java. It provides three beans:
SecurityFilterChain—authorizeHttpRequestsending inanyRequest().authenticated()(deny-by-default); only health/auth endpoints arepermitAll().PasswordEncoder→BCryptPasswordEncoder(adaptive; never MD5/SHA-1/plaintext —sec-weak-hash).CorsConfigurationSource— explicit origins/methods/headers,allowCredentials(true)only with exact origins.
Step 3 — Tune for the chosen auth model
- Cookie/session: delete the
.csrf(...).disable()and.sessionManagement(...)lines. CSRF protection stays ON. Add aformLogin/httpBasicor your login flow. - Stateless token: keep both lines; register the bearer filter from
jwt-authbeforeUsernamePasswordAuthenticationFilter. - Prefer
requestMatchers(HttpMethod.X, "...")over broad patterns; keep the matcher list ordered most-specific first.
What ships with it
2 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.
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.
- 6d ago First seen · 71 lines · 95 tokens per session scan A 21b4634d95ae
security-filter-chain is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 24d ago), licensed MIT. It adds 95 tokens to every session and 864 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
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.