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 sso-ss/vibe-ship-it --skill quick-checkgit clone --depth 1 https://github.com/sso-ss/vibe-ship-itWrote 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/sso-ss/vibe-ship-it/quick-check)<a href="https://agentmods.dev/skills/sso-ss/vibe-ship-it/quick-check"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/quick-check/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/sso-ss/vibe-ship-it/quick-check"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/quick-check.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.00050 | $0.00759 |
| Opus 5 | $0.00025 | $0.00380 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
quick-check 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 9d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Check
The fast quality check. 4 items. Takes under a minute. Good enough for "can I show my friend?"
The 4 Checks
1. Does It Load?
Open every page in the browser. Check:
- No blank/white pages
- No console errors (open dev tools → Console)
- No visible "Error" or "500" or "404" on the page
- Content actually renders (not just a loading spinner forever)
✅ Pass: all pages show content ❌ Fail: any page shows an error, stays blank, or shows a crash screen
2. Does The Main Thing Work?
Identify the PRIMARY user action (form submit, button click, navigation flow) and do it:
- If there's a form → fill it out and submit. Does it save? Does it show confirmation?
- If there's a CTA button → click it. Does it go somewhere?
- If there's a login → try logging in. Does it work?
- If it's a portfolio → do images load? Can you navigate between pages?
✅ Pass: the main action completes successfully ❌ Fail: the main action breaks, shows an error, or does nothing
3. Mobile?
Resize the browser to 375px width (iPhone SE). Check:
- Text is readable (not overflowing or cut off)
- Navigation is usable (hamburger menu works, or links are tappable)
- No horizontal scroll
- Content isn't overlapping
✅ Pass: looks usable on a phone ❌ Fail: layout is broken, text overflows, navigation is unusable
4. Can Everyone Use It?
Quick accessibility scan — not a full audit, just the obvious stuff:
- Images have
alttext (not empty) - Text is readable against its background (good contrast)
- Buttons and links have clear labels (not just an icon with no text)
✅ Pass: basics covered ❌ Fail: images missing alt text, unreadable text, or unlabeled buttons
Report Format
All Good
✅ Quick check — looks good.
1. ✅ All pages load fine
2. ✅ Form submits and saves correctly
3. ✅ Looks good on mobile
4. ✅ Accessibility basics covered
Ready to show someone!
Issues Found
Quick check — found 1 thing:
1. ✅ All pages load fine
2. ✅ Form submits correctly
3. ⚠️ Mobile: the headline text is too wide and gets cut off on phones
This won't break anything, but it'll look off on smaller screens.
Want me to fix it?
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.
- 9d ago First seen · 101 lines · 50 tokens per session scan A 76b1ae7e3fc0
quick-check is a skill published in the GitHub repository sso-ss/vibe-ship-it (12 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 759 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-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…