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 skills add bibinprathap/VeritasGraph --skill decisiongit clone --depth 1 https://github.com/bibinprathap/VeritasGraphWrote 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/bibinprathap/veritasgraph/decision)<a href="https://agentmods.dev/skills/bibinprathap/veritasgraph/decision"><img src="https://agentmods.dev/badge/skills/bibinprathap/veritasgraph/decision/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bibinprathap/veritasgraph/decision"><img src="https://agentmods.dev/badge/skills/bibinprathap/veritasgraph/decision.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00055 | $0.01471 |
| Opus 5.5 | $0.00022 | $0.00588 |
| Sonnet 5.5 | $0.00011 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
decision 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 1mo 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.
This is a copy
94% identical to decision — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/veritasreason:decision
Full decision lifecycle management. Usage: /veritasreason:decision <sub-command> [args]
record <category> "<scenario>" "<reasoning>" <outcome> <confidence>
Record a decision with full context.
from veritasreason.context import AgentContext
ctx = AgentContext(decision_tracking=True)
decision_id = ctx.record_decision(
category=category, # "loan_approval", "deployment", "hiring"
scenario=scenario, # natural-language situation description
reasoning=reasoning, # why this decision was made
outcome=outcome, # "approved", "rejected", "deferred"
confidence=float(confidence),
entities=entities or [],
decision_maker="ai_agent",
valid_from=valid_from, # optional ISO date string
valid_until=valid_until,
)
Output: Decision <decision_id> recorded | <category> | <outcome> (conf: 0.95)
query "<question>" [--hops N] [--hybrid]
Query decisions using natural language with multi-hop graph traversal.
from veritasreason.context import AgentContext
ctx = AgentContext(decision_tracking=True, advanced_analytics=True)
results = ctx.query_decisions(
query=question,
max_hops=int(hops) if hops else 3,
include_context=True,
use_hybrid_search="--hybrid" in args,
)
For structured lookups use DecisionQuery:
from veritasreason.context.decision_query import DecisionQuery
dq = DecisionQuery(graph_store=ctx.graph_store)
# dq.find_by_category(category, limit=100)
# dq.find_by_entity(entity_id, limit=100)
# dq.find_by_time_range(start, end, limit=100)
# dq.multi_hop_reasoning(start_entity, query_context, max_hops=3)
# dq.trace_decision_path(decision_id, relationship_types)
# dq.analyze_decision_influence(decision_id, max_depth=3)
Return: | ID | Category | Scenario | Outcome | Confidence | Timestamp |
precedents "<scenario>" [--category <cat>] [--advanced] [--hops N] [--as-of <date>]
Find similar past decisions using hybrid semantic + structural + vector search.
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.
- 1mo ago First seen · 198 lines · 55 tokens per session scan A f866130ed80e
decision is a skill published in the GitHub repository bibinprathap/VeritasGraph (325 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,471 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to decision, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
pinecone-research
Agent RAG and long-term memory with Pinecone.
memory-triage
Persistent long-term memory protocol powered by mem0. Evaluate conversations for durable facts worth storing via memoryadd. Handles identity, preferences, decisions, configurations, rules, projects, and relationships. Loaded by the openclaw-mem0 plugin when skills mode is active.
mem0
Mem0 Platform SDK for adding persistent memory to AI applications. TRIGGER when: user mentions "mem0", "MemoryClient", "memory layer", "remember user preferences", "persistent context", "personalization", or needs to add long-term memory to chatbots, agents, or AI apps. Covers Python SDK (mem0ai), TypeScript SDK…
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
mem0-cli
Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0…
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.