Borrowing it
Nothing to install: this file belongs to susomejias/rembric. 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/susomejias/rembric/main/.agents/skills/rembric-smoke-tests/SKILL.mdgit clone --depth 1 https://github.com/susomejias/rembricWrote 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/susomejias/rembric/rembric-smoke-tests)<a href="https://agentmods.dev/skills/susomejias/rembric/rembric-smoke-tests"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/rembric-smoke-tests/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/susomejias/rembric/rembric-smoke-tests"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/rembric-smoke-tests.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.00110 | $0.02612 |
| Opus 5 | $0.00055 | $0.01306 |
| Sonnet 5 | $0.00022 | $0.00522 |
| Haiku 4.5 | $0.00011 | $0.00261 |
Grade C, and why
rembric-smoke-tests 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
find /tmp -maxdepth 1 -name 'rembric-test-*' -mmin +60 -exec rm -rf {} + Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **HTTP**: `curl … | jq` against `http://localhost:<port>/api/<slug>/…` with `Authorization: Bearer …` and `Content-Type: application/json`. Parse responses with `jq`, not regex. How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rembric smoke pattern
Real-stack verification of a change before opening the PR. Read docker-compose.dev.yml, apps/server/Dockerfile, and package.json::dev:docker:up for the source of truth on ports, mounts, and the dev target — this file gives you only the pattern that survives those changing.
0. Preflight: free the RAM the build needs
/tmp is a tmpfs on this box, so everything under it is RAM. Every vitest run leaves a rembric-test-* directory behind and nothing cleans them: 1624 of them once held 8 GB, leaving 2.4 GB free, and pnpm run dev:docker:up died with exit code: 137 (Killed) mid-pnpm install. That failure reads like a network or lockfile problem and is neither.
free -h # the `shared` column is the tmpfs
find /tmp -maxdepth 1 -name 'rembric-test-*' -mmin +60 -exec rm -rf {} +
Keep the -mmin +60: other sessions may be mid-run, and a bare glob takes their fixtures with it.
1. Bring up from the change's worktree
cd <your-worktree>
[ -f .env ] || cp <main-worktree>/.env .env
pnpm run dev:docker:up # background OK
2. Verify YOUR source is mounted
The compose project name is global across worktrees, so docker compose up will silently attach to a stack another worktree already owns. Always confirm:
docker inspect rembric-dev --format '{{range .Mounts}}{{.Source}} -> {{.Destination}}{{println}}{{end}}'
Sources must point to the current worktree. If they don't, docker compose -f docker-compose.yml -f docker-compose.dev.yml down --remove-orphans from the owning worktree path, then up again from yours.
3. Wait healthy
until docker ps --filter name=rembric-dev --filter health=healthy --format '{{.Names}}' | grep -q rembric-dev; do sleep 3; done
4. Read port + bearer from sources of truth
- Container port: from
docker-compose.dev.yml::ports. - Admin bearer:
grep '^REMBRIC_ADMIN_TOKEN=' .env | cut -d= -f2-. Nevercat .env— the harness blocks it to keep secrets out of the transcript. - Default seeded project slug: from
apps/server/src/scripts/seed-dev.ts.
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.
- 12d ago First seen · 142 lines · 110 tokens per session scan C 1c0baabd3455
rembric-smoke-tests is a skill published in the GitHub repository susomejias/rembric (12 stars, last pushed 9d ago), licensed MIT. It adds 110 tokens to every session and 2,612 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
uat-testing
Run end-to-end User Acceptance Tests for Agent Brain features. Builds wheels, installs packages, starts a test server, runs tests, and reports results — all without permission prompts.
dogfood
This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.
gstack-qa
QA lead with real browser testing. Tests your app, finds bugs, fixes them with atomic commits, generates regression tests. Use when the user says "QA", "test this", "find bugs", "exploratory test", "QA this", or "test the app".
bugbug-automation
Automate Bugbug tasks via Rube MCP (Composio). Always search tools first for current schemas.
browser-automation
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping…