More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    The Lorekeeper: what your repo refuses to become

    1

    Mines your git history for what the team reverted, removed and declined, and writes a VISION.md of evidence-backed principles so agents stop proposing changes you would reject.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    The Lorekeeper: what your repo refuses to become

    The Lorekeeper: what your repo refuses to become

    Example session with this skill installed

    Coding agents keep proposing changes we would never merge. Write down what this repo refuses to become, as a VISION.md, based on its real history. gh is logged in, read-only.

    • Read your context and instructions
    • Compiled the the lorekeeper

    3. Maintainability and safety beat raw speed

    A large rewrite of the C code for speed is declined. The stated direction for compiled code is Rust (open PR #438). Small, clear fixes for real slowdowns are welcome.

    Evidence

    • #519 (faster C rewrite) closed by the maintainer, who prefers the Rust version for maintainability and safety.
    • ff06d77 (#522) merged a targeted fix for a quadratic striptags slowdown.

    $ python3 /tmp/vision.py check VISION.md
    VISION.md: 9 principles, 5 rulings, every cited sha exists

    check VISION.md

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

    About this skill

    Remembers every time you said no.

    Coding agents keep proposing changes that look fine and that your maintainers would reject on sight: a plugin system in a project that already removed one, a runtime dependency in a library that avoids them. The reasons are in your history. Nobody wrote them down.

    What it does

    1. A small Python script reads your local git history and prints an evidence digest: reverts, directories that no longer exist, commits that mostly deleted files, commit messages that say "remove", "drop", "instead of" or "rather than", merged work and high-churn files. Every row starts with a real commit sha.
    2. Optionally, with your own gh CLI, it adds PRs closed without merge (with the last comment) and the longest review threads.
    3. The agent reads the strongest leads and drafts 5 to 9 principles. Each one says what the repo resists and cites a commit sha or PR number. No evidence, no principle, unless you state it yourself.
    4. It stress-tests the draft with 3 to 5 hard hypothetical changes and asks you to rule on each.
    5. It writes VISION.md with your rulings, runs a check that every cited sha exists, and offers one pointer line for CLAUDE.md or AGENTS.md.

    What you get

    A short, reviewable file in your repo that tells any agent, and any new teammate, what this project will not become, and why, with links back to the moments the team decided.

    Who it is for

    Maintainers of open source libraries, tech leads of long-lived services, and anyone who reviews a lot of agent-written PRs.


    Part of The Guild, agent skills by Sesisnando Neto: The Oathkeeper (sealed acceptance checks), The Quartermaster (quests and decisions), The Tracker (root-cause proof), The Archivist (memory hygiene), The Inspector (QA validation).

    Needs real history: it stops below 30 commits unless you force it. Commit messages are matched by keywords, so many rows are routine and the agent has to judge them. Shallow clones hide old history. PRs closed without merge are only found with gh on GitHub. The principles are the agent's reading of the evidence until a maintainer rules on them.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Requires

    GitHub
    Git
    Python 3.8+
    Bash

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Allowed Hosts

    github.com

    File Scopes

    VISION.md
    (or
    docs/vision.md)
    reads
    git
    history
    only

    Read-only on git and GitHub. Writes VISION.md in your working tree. The optional --gh step reads PR titles and comments through your own gh CLI (api.github.com); nothing is posted. Never commits, pushes, comments or reviews.

    Listedtoday

    What's inside

    Frequently Asked Questions

    No. The script only reads your local git history with git. If you pass --gh, it calls GitHub through your own gh CLI to read PR titles and comments; nothing is posted.

    No. Reverts, removed directories, removal commits, merges and churn all come from local git. GitHub only adds closed-unmerged PRs and long threads, which are strong evidence when you have them.

    The skill tells it not to, and the check command flags any principle with no sha or PR, and any sha that does not exist in your repo. PR numbers cannot be confirmed offline, so the check lists them as notes.

    The agent records its recommendations as 'not yet ruled' and keeps the file as a draft. Only a maintainer's answer turns it into a ruling.

    Yes for everything local. The optional PR part uses gh, so it is GitHub only.

    No. It writes VISION.md in your working tree and offers the pointer line. You decide when and how the team sees it.

    New in Agents & Orchestration