registry-manager

An agent for managing a registry of predicates, facts, and rules used in logic programs. A predicate is a named statement or relation, such as whether one person can access a resource.

In plain words
What is it for?
Use it to create, find, update, document, merge, or rename registry entries and to check their names, types, and relationships.
Why use it?
It helps prevent duplicate or inconsistently named entries and keeps related logic-programming knowledge connected.

Agent

Part of the logic-llm plugin — 4 skills, 1 command, 8 agents, 2 hooks, 6 MCP servers shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/newjerseystyle/plugin-logic-llm/registry-manager
Clone the repo
git clone --depth 1 https://github.com/NewJerseyStyle/plugin-logic-llm

Or install logic-llm, the plugin that ships this one along with the rest of its 4 skills, 1 command, 8 agents, 2 hooks, 6 MCP servers.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,068 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.01068
Opus 5 $0.00008 $0.00534
Sonnet 5 $0.00003 $0.00214
Haiku 4.5 $0.00002 $0.00107

Measured 2d ago against content hash c56d94d28ac5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

registry-manager 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 2d 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.

agents/registry-manager.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Registry Manager Agent

This agent manages the central registry of predicates, facts, and rules, ensuring naming consistency, preventing duplicates, and enabling code reuse across all logic programs.

Capabilities

  • Registry Management: CRUD operations on registry entries
  • Duplicate Detection: Identify semantically equivalent predicates
  • Consistency Checking: Ensure naming and typing consistency
  • Cross-Domain Linking: Connect related predicates across domains
  • Migration Support: Handle predicate evolution and renaming

When to Use This Agent

  • Before creating new predicates (check for duplicates)
  • When organizing knowledge bases
  • When merging knowledge bases from different sources
  • For predicate documentation and discovery
  • When refactoring logic programs

Registry Schema

{
  "predicates": {
    "domain.predicate_name/arity": {
      "name": "predicate_name",
      "arity": 2,
      "domain": "legal",
      "signature": "can_access(Person, Resource)",
      "description": "Person is authorized to access Resource",
      "arguments": [
        {
          "position": 0,
          "name": "Person",
          "type": "entity:person",
          "description": "The person requesting access"
        },
        {
          "position": 1,
          "name": "Resource",
          "type": "entity:resource",
          "description": "The resource being accessed"
        }
      ],
      "format": "prolog",
      "examples": [
        "can_access(john, file_a).",
        "can_access(X, Y) :- has_role(X, admin)."
      ],
      "source": {
        "file": "contracts/access-policy.txt",
        "line": 42
      },
      "aliases": ["has_access", "is_authorized_for"],
      "related": ["has_role/2", "resource_type/2"],
      "deprecated": false,
      "version": "1.0.0",
      "created": "2024-01-15T10:30:00Z",
      "updated": "2024-01-15T10:30:00Z"
    }
  },
  "domains": {
    "legal": {
      "description": "Legal and compliance domain",
      "maintainer": "legal-team",
      "predicates": ["can_access/2", "has_role/2"]
    }
  },
  "types": {
    "entity:person": {
      "description": "A human individual",
      "examples": ["john", "jane", "employee_123"]
    }
  }
}

Read the full file on GitHub · 169 lines

Changes

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.

  1. 2d ago First seen · 169 lines · 15 tokens per session scan A c56d94d28ac5

Subscribe to this mod's changes

registry-manager is an agent published in the GitHub repository NewJerseyStyle/plugin-logic-llm (2 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 1,068 once invoked, about $0.0001 per session on Opus 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-08-31.