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 fabioc-aloha/Alex_Skill_Mall --skill extension-audit-methodologygit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/extension-audit-methodology)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/extension-audit-methodology"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/extension-audit-methodology/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/fabioc-aloha/alex_skill_mall/extension-audit-methodology"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/extension-audit-methodology.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.00032 | $0.01336 |
| Opus 5.5 | $0.00013 | $0.00534 |
| Sonnet 5.5 | $0.00006 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
extension-audit-methodology 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extension Audit Methodology
Find quality issues standard code review misses — before release, not after deployment.
Pattern Overview
A systematic 5-dimension audit framework for VS Code extensions to identify code quality issues beyond standard linting. Produces actionable recommendations with evidence-based prioritization.
Problem Solved: Standard code review catches logic bugs and style issues, but misses extension-specific quality problems like orphaned commands, blocking I/O in UI threads, debug noise in production, and leftover dependencies from removed features.
When to Use:
- Before major release (milestone versions)
- After significant refactoring
- When performance degradation suspected
- Post-feature-removal cleanup
Time Investment: 2-4 hours for comprehensive audit + 4-8 hours remediation
5-Dimension Audit Framework
1. Debug & Logging Audit
Objective: Identify console statements and categorize by necessity
Method:
# Scan for all console statements
Select-String -Path src/*.ts -Pattern "console\.(log|debug|warn|error)" -Recurse
Categorization:
| Category | Keep? | Examples | Rationale |
|---|---|---|---|
| Enterprise compliance | ✅ | Audit logs, security events | Legal/regulatory requirement |
| User feedback | ✅ | TTS status, long-running ops | User-facing information |
| Critical errors | ✅ | Unrecoverable failures | Debugging user-reported issues |
| Setup verbosity | ❌ | "Loading CSS..." | Noise during normal operation |
| Migration debugging | ❌ | Version upgrade steps | Temporary development artifacts |
2. Dead Code Detection
Commands Cross-Check:
- Find registered commands in
extension.ts - Find command contributions in
package.json - Find command invocations in UI/views
- Identify: broken (in UI, not registered), dead (registered, never invoked)
3. Performance Profiling
Blocking I/O Scan:
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 · 200 lines · 32 tokens per session scan A 23ce91de7452
extension-audit-methodology is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (5 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 1,336 once invoked, about $0.0001 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-03.
Other skills, from other repositories
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
code-review
Review code changes for concrete defects.
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.
ai-agents-config-catalog
Catalog of every configuration axis in this repo, env vars, commit markers, frontmatter keys, QA skip verdicts, and escape hatches, each with its enforcement point and abuse story, plus the checklist for adding a new flag safely. Use when you say what does a skip flag do, list escape hatches, can I skip this gate, add…
ai-agents-debugging-playbook
Symptom-to-triage playbook for this repo's recurring failures. Blocked pushes, drift gate reds, plugin bump reds, coverage pin trips, hook exit 143, session NONCOMPLIANT. Maps each symptom to a first command, discriminating experiment, fix path, and trap. Use when you say triage this failure, why is my push blocked…