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 AllenS0104/skill-browser --skill adapter-auditgit clone --depth 1 https://github.com/AllenS0104/skill-browserWrote 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/allens0104/skill-browser/adapter-audit)<a href="https://agentmods.dev/skills/allens0104/skill-browser/adapter-audit"><img src="https://agentmods.dev/badge/skills/allens0104/skill-browser/adapter-audit.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.00040 | $0.00839 |
| Opus 5 | $0.00020 | $0.00419 |
| Sonnet 5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
adapter-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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapter audit skill
Use this skill when you want to systematically audit and fix CLI adapter projects — for example, scanning all search adapters in opencli for missing url fields and batch-generating patches.
When to use
- auditing adapter output schemas for missing fields (url, timestamp, thumbnail, etc.)
- generating batch fixes across many adapters at once
- preparing multi-file PRs to upstream projects
- maintaining output consistency across a large adapter registry
Core workflow
1. Scan
Scan all adapters in the target project and classify each by:
- adapter type (YAML declarative vs TS/JS coded)
- which output fields are present
- which standard fields are missing
Standard fields to check:
url— direct link to the content itemtitle— content titleauthor— creator/author nametimestamp/date— publish or capture time
2. Classify fix type
For each missing field, determine the fix strategy:
| Situation | Fix strategy |
|---|---|
Field is computed internally but not in columns |
Add to columns list |
Field is computed but stripped by a map step |
Pass through the map step + add to columns |
| Field is not computed but can be constructed from existing data | Add construction logic + add to columns |
| Field requires external data not available in the API response | Skip or mark as "needs upstream API change" |
3. Fix
Apply fixes using the minimum change principle:
- For YAML adapters: add field to return object + map step + columns array
- For TS adapters: add field to return object + columns array
- Never change existing fields or behavior
- Only add new fields
4. Verify
After fixing, run the project's existing tests:
npm run build # ensure TS compiles
npm test # ensure nothing breaks
5. Submit
Create a single well-documented PR with:
- clear title describing the scope
- table showing before/after coverage
- per-adapter fix type classification
- risk assessment (should always be "additive only")
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.
- 8d ago First seen · 112 lines · 40 tokens per session scan A 75f1e2356610
adapter-audit is a skill published in the GitHub repository AllenS0104/skill-browser (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 839 once invoked, about $0.0002 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
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
architecture-review
Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.
code-review
Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.
anti-sycophancy
Rejects false validation; enforces objective critique, risk exposure, and constructive code alternatives. / TR: Yapay zekanın kullanıcı fikirlerini ve hatalı kod yönlendirmelerini körü körüne onaylamasını engeller. Yapıcı itiraz eder, riskleri gösterir ve doğru alternatifi sunar.
Git PR Reviewer
Pull Request (PR) creation and code review standards with constructive feedback and merge strategies. / TR: Pull Request (PR) oluşturma ve kod inceleme (code review) süreçleri için standartlar ve yapıcı geri bildirim.
code-orchestrator
Main orchestrator managing code architecture, refactoring, clean code principles, and adversarial code reviews. / TR: Kod yazma, güvenlik, eleştirel denetim, test ve mimari süreçlerini yöneten ana orkestratör.