REA is a reverse-engineering toolkit that lets coding agents investigate how software works, from app behavior to native binaries, even when source code is unavailable. It is for examining features, collecting evidence, explaining implementations, and building adapted versions for another stack. The catalogue add-ons connect coding agents to REA’s investigation workflow.
Borrowing it
Nothing to install: this file belongs to morluto/rea. 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/morluto/rea/main/.agents/skills/rea-ci-tests-audit/SKILL.mdgit clone --depth 1 https://github.com/morluto/reaWrote 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/morluto/rea/rea-ci-tests-audit)<a href="https://agentmods.dev/skills/morluto/rea/rea-ci-tests-audit"><img src="https://agentmods.dev/badge/skills/morluto/rea/rea-ci-tests-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/morluto/rea/rea-ci-tests-audit"><img src="https://agentmods.dev/badge/skills/morluto/rea/rea-ci-tests-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00047 | $0.01267 |
| Opus 5.5 | $0.00019 | $0.00507 |
| Sonnet 5.5 | $0.00009 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
rea-ci-tests-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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rea-ci-tests-audit — 91% identical, 108 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REA CI and tests audit
Establish which checks still catch real regressions and which costs can be removed without losing that protection. The outcome may be a verified fix, an evidence-backed recommendation, or an explicit decision to stop.
Follow the checkout's AGENTS.md, testing guide,
and contribution rules. Use their current commands
and pinned toolchain, rather than commands remembered from an earlier audit.
Preserve the requested scope: investigation alone does not authorize edits;
this skill does not grant permission to publish issues, push, or merge. Existing
user authorization still applies. Keep audit notes and raw results outside the
tracked tree, normally in a task-specific /tmp directory.
Establish the executed baseline
Fetch when the user asks for latest main. Pin the baseline SHA and inspected workflow revision; use an isolated worktree when changing or comparing code. Do not modify another task's checkout. Record dirty changes and the exact command, toolchain, host, selected tests, instrumentation, and prerequisites. An old run is evidence for its executed revision, even if main advances.
Trace workflow triggers, changed-path selection, job dependencies, reusable actions, package scripts, test discovery, artifact producers, and report gates through to the commands that actually execute. Include scripts, generated data, runtime registration, and subprocess boundaries missing from import graphs. Check positive and negative selection paths: required files must be discovered once per intended test configuration; deliberate platform/configuration repeats are separate coverage. A missing explicit test or missing required report must not turn green. Optional lanes may skip; preserve their stated prerequisites.
Use existing timing and failure artifacts to select suspicious families. Run relevant checks to establish a baseline; reserve a full local suite for broad CI diagnosis or uncertainty that focused checks cannot resolve. Do not rebuild or rerun an unchanged complete suite after every documentation edit.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 113 lines · 47 tokens per session scan A 997f3717eacb
rea-ci-tests-audit is a skill published in the GitHub repository morluto/rea (385,008 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,267 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
knowledge-engineering-quality-and-delivery
A project-wide quality and delivery workflow covering tests, release checks, builds, publishing, and bilingual documentation for Blade Code.
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
hatch3r-ci-pipeline
Designs and optimizes CI/CD pipelines. Covers stage design, test parallelization, artifact management, and pipeline performance.
blazemeter-integrations
Comprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD…