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 ArtemioPadilla/agent-triforce --skill security-auditgit clone --depth 1 https://github.com/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/security-audit)<a href="https://agentmods.dev/skills/artemiopadilla/agent-triforce/security-audit"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/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/artemiopadilla/agent-triforce/security-audit"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/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.00041 | $0.00857 |
| Opus 5.5 | $0.00016 | $0.00343 |
| Sonnet 5.5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
security-audit 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.
What it actually says
Perform a security audit on: $ARGUMENTS
If no specific scope is provided, audit the entire src/ directory.
Follow these steps:
SIGN IN:
- Run the SIGN IN checklist from your agent file
- Note areas of concern based on the scope and past findings
AUDIT:
- OWASP Top 10 systematic check:
- A01: Broken Access Control — check auth/authz on all endpoints
- A02: Cryptographic Failures — check encryption, key management, hashing
- A03: Injection — SQL, NoSQL, OS command, LDAP injection vectors
- A04: Insecure Design — business logic flaws, missing rate limits
- A05: Security Misconfiguration — default configs, verbose errors, CORS
- A06: Vulnerable Components —
npm audit/pip audit - A07: Auth Failures — weak passwords, missing MFA, session management
- A08: Data Integrity — deserialization, unsigned updates
- A09: Logging Failures — sensitive data in logs, missing audit trail
- A10: SSRF — server-side request forgery vectors
- Secrets scan: grep for API keys, tokens, passwords, connection strings
- Dependency audit: check all deps for known CVEs
- Smart contracts (if Solidity): reentrancy, integer overflow, access control, front-running
- Architecture review: Check dependency direction (business logic must not depend on frameworks), verify layer separation (no auth bypass through adapter shortcuts, no direct DB access from use cases)
- Test strategy review: Verify security-critical paths have tests, authentication/authorization flows are integration-tested, input validation has unit tests
License Compliance Scan
Scan all project dependencies for license compatibility with the project license (MIT):
- Detect dependency manifest:
requirements.txt,pyproject.toml(Python) orpackage.json(Node) - Check each dependency's license using
pip-licenses --format=markdown(Python) ornpx license-checker --json(Node). If tools unavailable, inspect manifests manually - Classify by compatibility:
- Pass (permissive): MIT, BSD-2-Clause, BSD-3-Clause, Apache-2.0, ISC, Unlicense, CC0-1.0, 0BSD
- Warning (weak copyleft): LGPL-2.1, LGPL-3.0, MPL-2.0, EPL-1.0, EPL-2.0 -- flag with explanation of linking implications
- Critical (strong copyleft): GPL-2.0, GPL-3.0, AGPL-3.0 -- incompatible with MIT distribution
- Critical (no license): Dependency has no detectable license -- cannot legally redistribute
- Output: License compatibility table in the security audit report with columns: Dependency, Version, License, Compatibility (Pass/Warning/Critical)
References: Skaife (2021), EPAM SolutionsHub (2023), Leroux (2025)
If any Critical finding: invoke the NON-NORMAL: Critical Vulnerability Response checklist from your agent file.
⏸️ TIME OUT — Run Verification Checklists (DO-CONFIRM): 7. Run through the Security Verification checklist from your agent file 8. Run through the Quality Verification checklist from your agent file 9. Issue verdict based on findings
SIGN OUT:
10. Write report to docs/reviews/security-audit-{date}.md
11. Write the Findings Handoff-to-Forja using the communication checklist
12. Run the SIGN OUT checklist from your agent file
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 · 65 lines · 41 tokens per session scan A a3fe5116f132
security-audit is a skill published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 857 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-08-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
pm
Project manager for GitHub issues: brainstorm design approaches, create structured issues optimized for LLM agent teams, triage and recommend what to work on next, audit and clean up stale issues, or deep-validate a single issue against the codebase. Triggers: create issue, plan work, new task, project manager, write…