Borrowing it
Nothing to install: this file belongs to mocaOS/cortex-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mocaOS/cortex-app/main/.claude/skills/verify/SKILL.mdgit clone --depth 1 https://github.com/mocaOS/cortex-appWrote 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/mocaos/cortex-app/verify)<a href="https://agentmods.dev/skills/mocaos/cortex-app/verify"><img src="https://agentmods.dev/badge/skills/mocaos/cortex-app/verify/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/mocaos/cortex-app/verify"><img src="https://agentmods.dev/badge/skills/mocaos/cortex-app/verify.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.00026 | $0.00628 |
| Opus 5.5 | $0.00010 | $0.00251 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade C, and why
verify scanned grade C with 2 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 2mo 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- Direct API: `KEY=$(docker exec cortex-backend printenv ADMIN_API_KEY)` then Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -H "X-API-Key: $KEY" http://localhost:8000/api/...`. How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying Cortex changes in the running app
The dev stack runs in Docker with hot-reloaded mounted source — no rebuild needed for frontend/backend edits:
cortex-frontend→ http://localhost:3000 (Next.js dev)cortex-backend→ http://localhost:8000 (FastAPI)cortex-neo4j→ 7474/7687
Auth
- UI login: real form at
/login; credentials from container env:docker exec cortex-frontend printenv ADMIN_EMAIL(andADMIN_PASSWORD). Login sets asessioncookie ANDadmin_api_keyin localStorage (the frontend sends it asX-API-Keyon fetches). - Direct API:
KEY=$(docker exec cortex-backend printenv ADMIN_API_KEY)thencurl -H "X-API-Key: $KEY" http://localhost:8000/api/....
Browser driving (Playwright)
Local node (nvm v23) works; browsers cache under ~/.cache/ms-playwright.
mkdir -p /tmp/verify-x && cd /tmp/verify-x
npm init -y && npm install playwright
npx playwright install chromium # if cached revision mismatches
ADMIN_EMAIL=$(docker exec cortex-frontend printenv ADMIN_EMAIL) \
ADMIN_PASSWORD=$(docker exec cortex-frontend printenv ADMIN_PASSWORD) \
node script.mjs
Login flow in a script: goto /login, fill input[name="email"] /
input[name="password"], click button[type="submit"], wait for URL to
leave /login. Then navigate anywhere (e.g. /documents).
- Document cards on
/documents: locate viadiv.glasscontainingh4[title*="<filename>"]; action buttons carrytitleattributes ("Download document", "View document", …). - To assert download-vs-tab behavior: listen for the page
downloadevent and the contextpageevent (popup).
Test data
- Upload a throwaway doc without triggering processing:
curl -H "X-API-Key: $KEY" -F "[email protected]" http://localhost:8000/api/upload(stayspendinguntil/api/documents/process-pendingis called). - Clean up:
curl -X DELETE -H "X-API-Key: $KEY" http://localhost:8000/api/documents/<id>.
Gotchas
- Frontend typecheck must run in the container (
docker exec cortex-frontend npx tsc --noEmit) — localnode_modulesis incomplete/root-owned. - Don't kick off document processing on real PDFs — it triggers LLM extraction (cost + long-running).
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.
- 2mo ago First seen · 60 lines · 26 tokens per session scan C 37fe6649253a
verify is a skill published in the GitHub repository mocaOS/cortex-app (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 26 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (harvests environment variables, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
test-production
Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.