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 MrPunyapal/laravel-auditor --skill laravel-audit-dsagit clone --depth 1 https://github.com/MrPunyapal/laravel-auditorWrote 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/mrpunyapal/laravel-auditor/laravel-audit-dsa)<a href="https://agentmods.dev/skills/mrpunyapal/laravel-auditor/laravel-audit-dsa"><img src="https://agentmods.dev/badge/skills/mrpunyapal/laravel-auditor/laravel-audit-dsa/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/mrpunyapal/laravel-auditor/laravel-audit-dsa"><img src="https://agentmods.dev/badge/skills/mrpunyapal/laravel-auditor/laravel-audit-dsa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 76 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- low Excessive Agency · line 69 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00051 | $0.01357 |
| Opus 5 | $0.00026 | $0.00678 |
| Sonnet 5 | $0.00010 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
laravel-audit-dsa 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 13d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel DSA / organizing-model audit
Audit the Laravel application for materially useful simplifications in data structures, state representation, control flow, algorithms, and ownership.
This is an audit-only exercise. Do not edit files, run mutating commands, implement recommendations, commit, or push. Read-only inspection and Laravel Auditor context tools are allowed.
You are the coordinator. Continue until every identifiable subsystem has been reviewed and the final audit is validated.
Credit: this workflow follows Aaron Francis's bounded, read-only subsystem audit method.
Tools to use first
php artisan auditor:context subsystems
php artisan auditor:context project_info
php artisan auditor:rules --applicable
Also use routes, models, database_schema, policies_authorization, jobs_events_schedules, and tests as needed. Prefer these over raw guesses.
Map each finding to a stable rule when one fits (AUD-DSA-001–AUD-DSA-004, or a core domain rule). Put subsystem and priority (p0–p3) in finding metadata.
1. Establish the coverage contract
Inspect the repository and inventory every identifiable subsystem. Start from auditor:context subsystems, then add any leftover app/ areas it did not list.
Give each subsystem:
- a stable ID and descriptive name
- an exact ownership boundary
- its key implementation files
- relevant public interfaces, major call sites, and tests
- a status:
queued,in review,recommend, orskip
Include HTTP, models, auth, database, jobs/queues, events, console, mail/notifications, tests, config, frontend/Livewire/Inertia/Filament when present, and generated-contract ownership where relevant.
Create one canonical report containing:
- the subsystem inventory
- confirmed opportunities
- explicit skip decisions
- cross-cutting patterns
- duplicates and superseded findings
- final priorities and dependencies
- an audit log
Treat this inventory as the coverage contract. Do not assume a catch-all row proves coverage.
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.
- 13d ago First seen · 144 lines · 51 tokens per session scan A 633924c34f47
laravel-audit-dsa is a skill published in the GitHub repository MrPunyapal/laravel-auditor (47 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 1,357 once invoked, about $0.0003 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-30.
Other skills, from other repositories
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
代码审查员
A code-review agent that examines changes for correctness, security, maintainability, performance, and test coverage.
capstone-radar
Unified A-F grading and ship/no-ship decisions for the 6-skill radar family (5 companions + capstone). Aggregates handoffs from data-model, ui-path, roundtrip, time-bomb, and ui-enhancer; owns 5 grep-reliable domains; tracks velocity; celebrates improvements. Triggers: "capstone radar", "can I ship", "grade codebase"…
time-bomb-radar
Finds deferred operations that crash on aged data -- code that passes every test but breaks weeks or months after release. Covers cascade deletes, cache expiry, trial paths, background accumulation, date-threshold transitions, and scheduled side effects. Triggers: "time bomb", "time-bomb", "/time-bomb-radar", "aged…
radar-suite
Unified entry point for the 6-skill radar family (5 companions + capstone). Routes to individual skills, runs targeted (Tier 2) or full (Tier 3) audit sequences, owns the unified ledger, and provides cross-skill operations (status, verify, ledger, link, deferred, fresh/no-fresh). Triggers: "radar suite", "full audit"…
radar-suite-axis-classification
Shared axis classification framework for all radar-suite skills. Every finding must be classified as axis1 (bug), axis2 (scatter), or axis3 (dead/smelly) before emission, with mandatory coaching fields and file:line citations to existing patterns in the audited codebase. Triggers: invoked by every radar before…