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 marcoguillermaz/Tierward --skill security-auditgit clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/marcoguillermaz/tierward/security-audit)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/security-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/security-audit/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/marcoguillermaz/tierward/security-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/security-audit.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.00000 | $0.05151 |
| Opus 5 | $0.00000 | $0.02576 |
| Sonnet 5 | $0.00000 | $0.01030 |
| Haiku 4.5 | $0.00000 | $0.00515 |
Grade A, and why
security-audit scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Live check** (staging): curl the staging URL and compare actual headers received vs configuration. A header present in config but absent in the response indicates a misconfiguration. How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration (adapt before first run)
Replace these placeholders:
[SITEMAP_OR_ROUTE_LIST]- file listing all API routes with method, path, roles, and grouping - e.g.docs/sitemap.md,docs/routes.md. If not configured, the skill discovers routes by scanning the project's route handler directories. Announce the discovered routes before proceeding.
Scope: API routes, middleware/proxy, row-level access control policies, data validation, response shapes, environment variables, database configuration, dependencies. For native stacks: secrets management, platform security (Keychain/Keystore/entitlements), input validation, signing credentials, sensitive data protection.
Out of scope: SEO, robots.txt, public crawlability, OpenGraph, sitemap.xml.
Do NOT make code changes. Audit only.
All findings are persisted to docs/refactoring-backlog.md via the backlog write-once protocol (.claude/rules/backlog-protocol.md).
Applicability check
Before any other step: read CLAUDE.md and check the Framework and Language fields.
- Web or API project (Framework is NOT
N/A - native app, OR route handler directories exist): proceed to Step 0 - full web audit (Steps 0–5) + Step 3e if the language is non-JS. - Native with API (Framework is
N/A - native appAND route handler directories exist): proceed to Step 0 - full web audit (Steps 0–5) + Step 3e (native checks run in addition to web checks). - Native only (Framework is
N/A - native appAND no route handler directories): skip Steps 0–5. Proceed directly to Step 3e (native-only audit). Then skip to Step 6 for the report.
Announce the execution path: Running security-audit - mode: [WEB | WEB+NATIVE | NATIVE-ONLY]
Step 0 - Target resolution
Parse $ARGUMENTS for a target: token.
| Pattern | Meaning |
|---|---|
target:role:admin |
Focus on admin routes |
target:section:export |
Focus on all export/bulk-data routes |
target:section:<other> |
Read [SITEMAP_OR_ROUTE_LIST] - find rows matching the section keyword, resolve to API routes and related route files |
| No argument | Full audit - all API routes |
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.
- 9d ago First seen · 381 lines · 0 tokens per session scan A c184a5c6b9bb
security-audit is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,151 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
harness-engineering
Use when the user asks to improve, fix, or build their repository's AI harness — AGENTS.md, rules, skills, commands, hooks, guardrails, CI sensors — or to act on harness-score audit findings and raise their maturity level.
codex-hud
Show Codex workspace context with local config, git state, hooks, and project hints. Standalone mode can show an expanded snapshot; patched Codex TUI footer mode is single-line. Use when the user says "codex-hud", "show Codex HUD", "status HUD", "workspace snapshot", or asks for richer Codex context.
address-conductor-comment
A workflow for handling pending Conductor code-review comments, including reading their discussion and assigning changes to subagents when appropriate.
explain-comment
A skill that reads a specified file or code range and adds explanatory comments in Japanese. The comments use a question style and focus on important logic, design choices, and side effects.
saleae-mcp-debugger
Use this skill for hardware-in-the-loop firmware capture and decode workflows through the Saleae Logic 2 MCP server.
build-feature
Full pipeline: evaluation -> spec -> implementation -> review -> QA.