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 agentlas-ai/agentlas-desktop --skill auditgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/audit)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/audit"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/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/agentlas-ai/agentlas-desktop/audit"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/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.00032 | $0.00513 |
| Opus 5.5 | $0.00013 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Purpose
Evaluates existing product interfaces and flows through direct step-by-step browser capture, producing an evidence-grounded UX, design, and accessibility audit report.
Preconditions
- The target product URL or interface and the specific user journey (e.g., onboarding, checkout, signup, settings) must be identified.
- Browser capture capability (such as
@agentlas-browseror@playwright) must be available. - Adhere to
$critical-overridesand$design-audit-framework. - Judge what the captures show against
$hig-checklist; when a finding needs a citation, route to the backing guideline with$hig-lookup. For a full guideline-graded review of a surface rather than a journey, hand off to$hig-review.
Steps
- Initialize & Navigate: Open the target flow and wait until the initial screen is fully loaded and visually stable.
- Step-by-Step Capture & Inspection:
- Advance through the user journey one action at a time.
- Capture a clean screenshot at each state and save it sequentially (e.g.,
01-start.png,02-form-filled.png). - Observe visual hierarchy, validation behaviors, loading states, empty states, keyboard focus, and contrast.
- Analyze Findings: For each step, note observed strengths, UX friction points, accessibility risks, and limits of screenshot-only inspection. Grade findings by consequence using the severity scale in
$hig-review-protocol, and state the guideline behind any rule-shaped claim. - Compose Inline Report:
- Assemble an inline markdown report pairing numbered steps directly with their corresponding screenshots.
- Include an executive summary, step-by-step breakdown, top-priority recommendations, and clear evidence limits.
- Optional Figma Board: If explicitly requested by the user, plot the accepted screenshots and notes onto a Figma canvas.
Outputs
- Sequentially saved flow screenshot files.
- Evidence-grounded inline UX and accessibility audit report.
Verification
- Ensure every reported issue and strength is tied 1:1 to an actual captured screenshot.
- Verify that no speculative claims or ungrounded opinions are presented as audit facts.
- Confirm that accessibility assessments clearly state what was visually observed versus what requires automated/screen-reader testing.
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 Changed · +3 lines 5572cc10a1f0
- 1mo ago First seen · 34 lines · 32 tokens per session scan A ad30b628c787
audit is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 513 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-08-31.
Other skills, from other repositories
architecture-diagram
How to draw and maintain the architecture diagram Ensemblr keeps for a workspace — ensemblrgetarchitecturediagram to fetch the stored one (it answers with null when nobody has drawn this workspace yet), the IR shape, how to derive it from the codebase, and ensemblrupdatearchitecturediagram to store it. Read this when…
frame-macos-notification
Realistic macOS notification banner with app icon, title, and body, suited to video overlays or product teasers.
winui-design
Read before writing or changing WinUI 3 XAML: choosing controls, pages and navigation, layout, Fluent Design, theming, accessibility, x:Bind, real samples, and checking that APIs exist with winapp find-api. Not for WPF or WinForms UI, even if the app uses the Windows App SDK.
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the…
openscreen-design
Use this skill to generate well-branded interfaces and assets for OpenScreen (an AI-native screen-recording studio & video editor), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
edit-figma-design
Create or update Figma designs directly from a written product or UI description using the Figma MCP authoring tools. Use when the user wants a mockup, wireframe, screen, component, flow, or concept designed in Figma from text, or wants to iterate on an existing Figma file from textual feedback. Despite the name, this…