vijaygopalbalasa

GitHub profile1 plugin in the catalog

Plugins by vijaygopalbalasa

1 plugins by vijaygopalbalasa in the catalog, most-starred first.

vijaygopalbalasacontract-necromancerHermes's done doesn't count until your tests pass. Type /necro freeze in your project: it finds your tests and the command that runs them, writes necro.toml, locks the test files and the settings that choose what runs by hash, and runs them once to say where they stand. When Hermes says it is finished, the plugin runs them itself at the verify step and sends Hermes back with the failing test named; the final reply says when Hermes was sent back and ends with a receipt anyone can re-check, also in a fresh clone (/necro verify: CONFIRMED, MISMATCH or SUPERSEDED). Edits to locked tests are blocked, and any change that gets through fails the check. Only a person can freeze: /necro is a slash command the agent cannot type, and from its shell freezing refuses. A prompt or skill can only ask the model to test its work; these hooks run whether it asks or not. Disclosure — runs the test commands in the project's frozen necro.toml (split into words, no shell; a command the person types after /necro freeze that uses shell syntax such as && or | is stored and run as sh -c) in the project folder with the user's permissions, unsandboxed, with a small environment (no API keys unless a contract names them), at /necro freeze, from pre_verify, from the final-reply hook when project files changed or the reply claims done, from the necro_check tool (the model can call it but cannot change the commands) and from /necro check; verify re-runs them only for a lock the person approved for that folder, or with --run; with no necro.toml, /necro freeze reads file names and test settings (package.json, pyproject.toml, setup.cfg, tox.ini, Cargo.toml) to pick the command, and may run that command's Python with -c "import pytest" in an empty folder (a project interpreter such as .venv/bin/python only when the person typed it); contracts run with the PATH of the Hermes process that runs the agent, minus Hermes's own runtime; reads project files to hash them but never opens credential files such as .env (their pins hold only presence, size and file times); never opens or follows a link (its pin is the link's own text); runs git ls-files with fsmonitor and hooks off and the same small environment; writes .necro/ and necro.toml in the project, and approval records plus the key that seals them (HMAC) under the plugin's data directory; adds NECRO_AGENT_SESSION to the environment of commands the agent runs; runs ps when someone runs freeze, approve or unfreeze from a shell; no network, no telemetry, no credentials, no background processes.Communitytools