audit-my-app
Sweep a whole running web app for what is broken, without writing a script or knowing the codebase. Clicks every reachable control and reports dead buttons, console errors, failed requests, and places where the API and the screen disagree.
Install / Use
npx skills add reticlehq/reticle --skill audit-my-appInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of audit-my-app
audit-my-app scores 87/100 on our quality scale, 617th of 1,156 Content & Media skills we index.
Its SKILL.md is 4.2 KB long, split into 6 sections with 6 code examples: a solid amount of guidance for an agent.
With 1,271 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 10 days ago, so audit-my-app is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
audit-my-app compared with similar skills
All 4 of these similar skills score higher than audit-my-app; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| audit-my-app (this skill)by reticlehq | 87 | 1.3k | 10d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
| crawl4aiby unclecode | 100 | 87.5k | today | MCP Server |
Frequently asked questions
- How do I install audit-my-app?
- Run
npx skills add reticlehq/reticle --skill audit-my-app. The install tabs above show the steps for each supported agent. - Which AI agents does audit-my-app work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is audit-my-app safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is audit-my-app still maintained?
- The repository was last updated 10 days ago, so audit-my-app is actively maintained.
Skill content
View source on GitHubname: audit-my-app description: Sweep a whole running web app for what is broken, without writing a script or knowing the codebase. Clicks every reachable control and reports dead buttons, console errors, failed requests, and places where the API and the screen disagree. Use on an unfamiliar codebase, before a release, after a big merge or dependency bump, when the user asks for a smoke test or a health check, or when someone says "just check everything still works". license: Apache-2.0 metadata: version: 3.5.0 homepage: https://www.reticle.sh repository: https://github.com/reticlehq/reticle
Sweep the whole app and report what is broken
You do not need to understand the codebase to check it. Reticle drives every reachable control in the running app and reports the anomalies. Not installed? RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then the install-and-verify skill.
1. Ask the app what it can do
reticle_run({ tool: "reticle_capabilities", args: { sessionId } })
About 1 KB, and it is the app describing its own testable surface: every registered testid, every domain signal, the stores, and the saved flows with their steps. That beats snapshotting the DOM and inferring intent from element names, and it is the cheapest orientation available.
2. Click everything
reticle_run({ tool: "reticle_verify", sessionId, args: { action: "crawl", maxSteps: 25 } })
{
"interactiveFound": 3,
"stepsRun": 3,
"anomalies": [],
"counts": { "consoleErrors": 0, "failedRequests": 0, "deadControls": 0, "contradictions": 0 },
"visited": ["- textbox \"Email\"", "- button \"Sign in\""],
"truncated": false
}
deadControls and contradictions are the two counts that mean a real problem. Console errors and failed requests are worth reading but a busy app produces both innocently. A dead control is a button wired to nothing; a contradiction is a channel disagreeing with what the screen showed.
It clicks everything, so point it at a dev environment. maxSteps bounds it and defaults to 25. Want a non-destructive pass first: what is reachable, without touching it? reticle_run({ tool: "reticle_explore", sessionId }).
Do not hand-roll this sweep. The obvious version (click each control, assert no console error) passes on exactly the bug you are sweeping for, because a dead button throws nothing.
3. Compare what the API said against what rendered
reticle_run({ tool: "reticle_reconcile", sessionId })
The API returned ten rows, the table shows nine, nothing errored. Neither the network log nor the DOM is wrong on its own. Only the comparison catches it, and nothing else you can run makes that comparison.
4. Find the parts nobody exercised
reticle_run({ tool: "reticle_verify", sessionId, args: { action: "coverage" } }) // { total, exercised, untouched }
And if the project already has saved flows, ask whether they prove anything:
reticle_run({ tool: "reticle_domain", sessionId })
// → { flowCount, coverage: { asserted, presenceOnly, assertionFree }, gaps: { declaredUntestedSignals, … } }
A suite of forty flows where thirty-one assert nothing is a suite that will stay green through any regression. That number is usually the most alarming thing in the whole audit, and nothing else reports it.
5. Report
Lead with the counts, then one line per real finding with its file:line from reticle_look { action: "element" }. Separate:
- Broken: dead controls, contradictions, failed requests, errors thrown during the sweep.
- Unverified:
untouchedcontrols andassertionFreeflows. Not known to be broken; known to be unchecked. - Pre-existing: console errors that were already there before the sweep started. Say so, so nobody attributes them to today's change.
Do not report a clean audit over a partial one. If truncated is true or maxSteps cut the sweep short, say what was not reached. A silent cap reads as "everything is fine" when it means "I stopped".
Full capability reference: curl https://docs.reticle.sh/capabilities.md. Everything else: curl https://docs.reticle.sh/llms.txt.
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.5kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
