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.
npx agentmods add skills/newjerseystyle/plugin-logic-llm/logic-registernpx skills add NewJerseyStyle/plugin-logic-llm --skill logic-registergit clone --depth 1 https://github.com/NewJerseyStyle/plugin-logic-llmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/newjerseystyle/plugin-logic-llm/logic-register)<a href="https://agentmods.dev/skills/newjerseystyle/plugin-logic-llm/logic-register"><img src="https://agentmods.dev/badge/skills/newjerseystyle/plugin-logic-llm/logic-register.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
logic-register 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/logic-register
Register and manage predicates, facts, and rules in the logic knowledge registry.
Description
This skill manages the central registry that tracks all predicates, facts, and rules across the knowledge base. It ensures naming consistency, prevents duplicates, and enables code reuse across conversions.
Usage
/logic-register [command] [options]
Commands
add- Register new predicates or rulessearch- Search for existing predicateslist- List registered itemsupdate- Update predicate descriptions or metadatalink- Link related predicates across domainsexport- Export registry to file
Options
--domain <name>- Filter by domain--type <predicate|fact|rule>- Filter by type--format <json|prolog|clingo>- Output format
Examples
/logic-register add --domain legal "canAccess(Person, Resource) ::: Person is authorized to access Resource"
/logic-register search "access"
/logic-register list --domain legal --type predicate
/logic-register export --format json ./registry-backup.json
Registry Structure
Each registry entry contains:
{
"name": "canAccess",
"arity": 2,
"domain": "legal",
"type": "predicate",
"signature": "canAccess(Person, Resource)",
"description": "Person is authorized to access Resource",
"arguments": [
{"name": "Person", "type": "entity", "description": "The person requesting access"},
{"name": "Resource", "type": "entity", "description": "The resource being accessed"}
],
"examples": ["canAccess(john, confidential_files)"],
"source": "contracts/access-policy.txt",
"created": "2024-01-15T10:30:00Z",
"aliases": ["hasAccess", "isAuthorized"],
"related": ["hasRole", "resourceClassification"]
}
Deduplication
The registry prevents duplicate predicates by:
- Checking for exact name matches
- Checking for semantic similarity in descriptions
- Suggesting existing predicates when creating new ones
- Maintaining aliases for the same concept
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.
- 3d ago First seen · 101 lines · 0 tokens per session scan A b965701dc851
logic-register is a skill published in the GitHub repository NewJerseyStyle/plugin-logic-llm (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 645 tokens. 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.
Other skills, from other repositories
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.