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 instructions/dallionking/ui-validation-kit/agents-mdgit clone --depth 1 https://github.com/Dallionking/ui-validation-kitWhat 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.00843 | $0.00843 |
| Opus 5 | $0.00421 | $0.00421 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
ui-validation-kit AGENTS.md 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lionspaw-academy-skill AGENTS.md — 89% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus — Code Intelligence
This project is indexed by GitNexus as ui-validation-kit (607 symbols, 594 relationships, 0 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
If any GitNexus tool warns the index is stale, run
npx gitnexus analyzein terminal first.
Task tracking & execution (Standard Workflow — 2026-07-12)
- Tasks live in Linear (workspace dallion-king, project Dev Tools, team DAL); GitHub is the PR/code loop. New persistent task → Linear issue (wave-labeled).
- Builds run through Orca: pull the Linear task →
orca status→ orchestrator session (Fable/Claude side or Sol/Codex side per model lanes) →~/.local/bin/orca-dispatch-taskper task (worktree waves, depth-1 workers) → gates (Greptile review + Codex cross-model + coordinator) → PR → merge → cleanup per the ownership ledger. - Loop spec:
~/.claude/references/loop-registry.md(Core-5: BUILD, TICK+TIMER, CLEANUP, PR-SWEEP, GAP). Constitution:~/AGENTS.md.
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
gitnexus_impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
gitnexus_detect_changes()before committing to verify your changes only affect expected symbols and execution flows. - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
gitnexus_query({query: "concept"})to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use
gitnexus_context({name: "symbolName"}).
Never Do
- NEVER edit a function, class, or method without first running
gitnexus_impacton it. - NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
- NEVER rename symbols with find-and-replace — use
gitnexus_renamewhich understands the call graph. - NEVER commit changes without running
gitnexus_detect_changes()to check affected scope.
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.
- 2d ago First seen · 48 lines · 843 tokens per session scan A a9c2b34097f8
ui-validation-kit AGENTS.md is an instructions file published in the GitHub repository Dallionking/ui-validation-kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 843 tokens to every session, about $0.0042 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.
Other instructions, from other repositories
autotask-mcp dev_workflow.instructions.md
Guide for using Taskmaster to manage task-driven development workflows.
Table-GitHub-Capability-Router AGENTS.md
Instructions for duoduoler-ops/Table-GitHub-Capability-Router: This is the canonical repository instruction file. Client-specific compatibility files must point here instead of duplicating these rules.
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
wiki_ticket_sdd CLAUDE.md
Instructions for SpillwaveSolutions/wiki_ticket_sdd, covering acme platform, work tracking policy and work taxonomy.
super-backlog CLAUDE.md
Instructions for adam-s-k-i/super-backlog: This project uses the combined Backlog.md + Superpowers workflow. Read the integration block in AGENTS.md (section between SUPER-BACKLOG markers) and follow it. Tasks are managed exclusively through the backlog CLI.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.