Is Redpen free, and what does this skill include?

Yes. This listing is free and provides instructions for the MIT-licensed Redpen CLI. The executable is separately available as redpen-cli@0.4.0 from npm; it is not bundled into this skill. First use may download the pinned package after any permission required by your agent.

Will it work in ordinary web chat?

Verification requires a shell-capable agent with Node.js 18+, npm, Git and access to your local repository. Installing a skill does not grant those capabilities. Without them, the skill explains the missing prerequisites and does not generate a verdict.

Does DONE mean my code is correct in every case?

No. DONE means the configured required criteria were proven and no claim was contradicted under the selected policy. Unsupported claims remain UNVERIFIED. Strict claims mode requires every claim to be proven. Passing tests or changed files do not prove general correctness or API compatibility.

Can Redpen verify work that was finished before I started it?

It can run fresh project checks, but it cannot invent a historical baseline or attribute earlier edits to the task. For task-specific evidence, start Redpen before implementation.

Does this skill capture transcripts or run completion hooks?

No. This Agensi edition records a concise completion summary via redpen claims and verifies it before returning a receipt. No hooks, automatic transcript capture, new credentials or Redpen account are required.

Where can I report a problem?

Open an issue at https://github.com/ChiragArora31/Redpen/issues with your runtime version, expected behavior and a minimal reproduction. Remove secrets, private source and transcripts. For security issues, follow the repository SECURITY.md.

Redpen — Verify Coding-Agent Work

Example session with this skill installed

Use Redpen for this task. Fix null cursor pagination, add a regression test that fails on the original implementation and passes on the fix, and return an evidence receipt. Keep any unsupported compatibility claims visible.

Read your context and instructions
Compiled the redpen

Reproducible CLI demonstration

The receipt below was generated by the published redpen-cli@0.4.0 on a disposable Git repository. The bug fix, regression test and completion claims were scripted fixtures; this is real CLI verification, not a recording of an Agensi agent session. The baseline was saved before the fix.

Redpen evidence receipt

Task: Fix null cursor pagination

Verdict: DONE (1 agent claim remains unverified)
Checked: 2026-10-17T08:43:51.824Z
Summary: 9 proven · 0 failed · 1 unverified
Claim policy: Required criteria must be proven; contradicted claims block DONE

Definition of done

✓ PROVEN — Implementation changed (required)
- 2 files changed · +2 -1
- Evidence: Changes made after the task started were found.
✓ PROVEN — Regression coverage (required)
- tests/null-cursor.test.mjs
- Evidence: 1 test file changed.
✓ PROVEN — Tests pass (required)
- npm run test · exit 0
- Evidence: npm run test → exit 0 in 185ms
✓ PROVEN — Build passes (required)
- npm run build · exit 0
- Evidence: npm run build → exit 0 in 121ms
✓ PROVEN — Null cursor regression reproduces the bug (required)
- “null cursor starts at beginning” fails with an assertion on the baseline and passes on the current snapshot. This proves the tested case, not general correctness.
- Evidence: node --test tests/null-cursor.test.mjs · exit 1
- Evidence: node --test tests/null-cursor.test.mjs · exit 0

Agent claims

✓ PROVEN — “Updated src/page.mjs.”
- src/page.mjs · +1 -1
- Evidence: src/page.mjs changed after this task started.
✓ PROVEN — “Added regression coverage.”
- tests/null-cursor.test.mjs
- Evidence: 1 test file changed.
✓ PROVEN — “All tests pass.”
- npm run test · exit 0
- Evidence: npm run test → exit 0 in 185ms
✓ PROVEN — “Build succeeds.”
- npm run build · exit 0
- Evidence: npm run build → exit 0 in 121ms
? UNVERIFIED — “No breaking changes.”
- No deterministic evidence is available. Redpen doesn't guess.

Generated by Redpen. Command output and the agent's full completion are omitted; review the receipt before sharing.

What happens next

The required task criteria passed. “No breaking changes” remains unverified; tests do not establish general compatibility. A separate strict-claims run returned NOT DONE. After changing the implementation, the saved receipt returned CHECK NEEDED, and a fresh verification failed. Review unresolved claims before relying on the handoff.

Connects securely to your tools. The creator never sees your data.

About this skill

“Done” is a claim. Evidence makes it true.

Redpen helps your coding agent establish what a task requires, record its completion claims, and check those claims against fresh repository evidence before handing work back.

What you get

A task-specific definition of done established before editing.
Independent test and build execution, with Git evidence for implementation and test changes.
A readable receipt separating PROVEN, FAILED and UNVERIFIED items.
Stale-evidence detection when files change after a check.
Optional strict claim verification and a focused JavaScript regression-proof beta.

Start here

In a shell-capable coding agent with your local Git repository open, ask: “Use Redpen for this task. Fix the bug, add regression coverage, and return an evidence receipt.”

This free Agensi edition provides the workflow instructions. The runtime is the separately published, MIT-licensed redpen-cli@0.4.0 package. Node.js 18+, npm and Git are required. First use may download that pinned package from npm after any required permission; no global installation or project dependency changes are needed.

Honest limits

Passing tests do not prove general correctness, API compatibility or the absence of breaking changes. Unsupported claims remain UNVERIFIED. The focused regression-proof beta supports one named, dependency-free JavaScript node:test assertion case; richer projects use their normal configured checks.

This edition has no completion hooks, hosted verification service or automatic transcript capture. Ordinary web chat without shell and repository access cannot run it. Agent-specific session adapters are not promised.

Local execution and privacy

Redpen runs locally and has no telemetry or hosted backend. Agensi and your agent provider have their own data policies. Project checks execute repository code with the environment’s permissions and may access files or the network. Receipts can contain project-derived information: review before sharing.

Built and maintained by Chirag Arora. Source, documentation and issue reporting: https://github.com/ChiragArora31/Redpen

How to use

Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

Fresh listing

Recently published to Agensi

Free forever

No account required to browse

Redpen — Verify Coding-Agent Work