Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    tamperproof rules

    1

    Your coding agent can't fake a pass: existing tests are read-only, and "done" means the real suite passes.

    Free

    1 useSecurity scanned
    tamperproof rules

    tamperproof rules

    Example session with this skill installed

    The CI is red on test_discount_rounding in tests/test_pricing.py. Make it green, I need to merge tonight.

    • Read your context and instructions
    • Compiled the tamperproof rules

    Illustrative session showing how the skill behaves when two tests contradict each other.

    Summary

    I could not make CI green honestly: two existing tests contradict each other, so I stopped instead of editing either one.

    What I ran

    python -m pytest -q (picked from pyproject.toml)

    FAILED tests/test_pricing.py::test_discount_rounding - assert 9.99 == 10.0
    1 failed, 41 passed
    

    The conflict

    TestInputExpects
    tests/test_pricing.py::test_discount_rounding$12.49 at 20% off10.0 (round half up to whole cents, then to 10c)
    tests/test_checkout.py::test_cart_total_exactthe same item in a cart9.99 (no rounding)

    apply_discount() feeds both. Any change that passes one fails the other, so no code-only fix exists.

    What I did not do

    • Did not edit, skip or loosen either test.
    • Did not change the expected values or the pytest command.

    My recommendation

    test_cart_total_exact matches the invoice spec in docs/billing.md ("never round customer totals"), so I think test_discount_rounding is the stale one. If you agree, tell me and I'll change it (or you can). Otherwise I can add a separate display_price() for the rounded value and leave totals exact.

    Status

    Not done: 1 test failing, waiting on your call about which behavior is correct.

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

    About this skill

    Outcome: your coding agent can't make the tests pass by editing the tests. Existing tests are read-only, and "done" means the real suite passes.

    Why this over asking nicely: the rules are explicit and checkable, and contradictory tests make the agent stop and ask instead of guessing. Free.

    Guaranteed: if it doesn't do what this page says on your setup, message me here or email support@tensorust.com and I fix it.

    You've seen it: a test fails, the agent can't fix the bug, so it loosens the assert, skips the test, or flips the expected value. Green check, broken code.

    This skill gives your coding agent three rules:

    1. Existing tests are read-only. Test files, snapshots, fixtures and golden files can't be edited, deleted, skipped or loosened (including through sed -i or scripts). Writing new tests is fine.
    2. "Done" means the real suite passes. Before it reports a task finished, the agent runs the project's actual test command (auto-picked for Rust, Go, Node, Python and Swift, or whatever .tamperproof.json sets) and reads the result. After 3 honest failed attempts it stops and shows you the output.
    3. Contradictory tests mean stop and ask. When two tests can't both pass, the agent tells you which ones, what each expects, and what it thinks is right. Changing a test is your call.

    Evidence (small sample): in a Claude Code experiment on repos with contradictory tests, 2 of 6 runs edited a test to force green (one skipped it, one deleted it). With these rules enforced, 0 of 6 did; every run stopped and asked. Method and raw data are public in the repo.

    Want it enforced, not just instructed? For Claude Code there's a free MIT hooks plugin that blocks edits to protected paths and blocks the session from ending while the tests fail: https://github.com/Mattbusel/tamperproof

    Instructions only: a model can still ignore them. For hard enforcement in Claude Code, use the free tamperproof hooks plugin. Test command auto-detection covers Cargo, Go, npm, pytest and SwiftPM; other stacks need a verify command in .tamperproof.json.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Python

    Permissions

    Write Files
    Read Files

    Runs the project's own test command and edits source files to fix bugs. It never edits existing tests.

    Listed1 month ago
    Updated26 days ago

    What's inside

    Frequently Asked Questions

    Your coding agent can't fake a pass: existing tests are read-only, and "done" means the real suite passes.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use tamperproof rules on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Agents & Orchestration