Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wrg32786/aigent-osnpx agentmods add skills/wrg32786/aigent-os/reconcileWrote 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/wrg32786/aigent-os/reconcile)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/reconcile"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/reconcile/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/wrg32786/aigent-os/reconcile"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/reconcile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00631 |
| Opus 5.5 | $0.00010 | $0.00252 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
reconcile 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reconcile - attention reconciliation
This measurement leg reports attention drift. It never edits priorities, daily notes, goals, or runtime state.
Run:
node daemons/nightly-reconcile.mjs --root <aigent-root> --as-of <fire-date>
Use literal output and exit status as the checkpoint evidence.
Required intended-share input
Read vault/memory/ACTIVE_PRIORITIES.md and locate explicit Tier-1 projects
with intended percentages. Accepted forms:
| Tier | Project | Intended share |
| 1 | [[Project Name]] | 40% |
or:
Tier 1 - [[Project Name]] - intended 40%
Shares are integers from 1 through 100 and the Tier-1 total must be at most 100. Names or aliases must resolve to a project note or an explicit canonical name in the priorities file.
No intended shares returns nonzero:
RECONCILE FAIL reason=intended-share-input-absent projects=0
This is a configuration failure, never permission to invent shares.
Seven-day measurement
- Select valid
vault/daily/YYYY-MM-DD.mdnotes inside the exact calendar windowas_of-6d .. as_of. A missing day contributes no mentions. - Per project and note, count at most:
- 3 points for a heading or heading wikilink;
- 2 points for a body wikilink to a canonical note or alias;
- 1 point for an exact plain-text name.
- One occurrence receives only its highest applicable weight.
- Track project references outside Tier 1 as non-Tier-1 attention.
- Compute
actual = project points / all project points * 100, rounded to one decimal.
A zero denominator returns
RECONCILE FAIL reason=no-measurable-project-attention.
Drift predicates
- Tier-1 drift:
actual < 0.40 * intended. - Combined non-Tier-1 drift: actual share over 25 percent.
Output raw points, actual share, intended share, thresholds, drift decisions, and source paths so the arithmetic is reproducible:
RECONCILE PASS window=YYYY-MM-DD..YYYY-MM-DD notes=<N>
project=<name> points=<N> actual=<N.N>% intended=<N>% threshold=<N.N>% drift=<yes|no>
non_tier_1 points=<N> actual=<N.N>% drift=<yes|no>
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 · 86 lines · 25 tokens per session scan A 8e017ece17e7
reconcile is a skill published in the GitHub repository wrg32786/aigent-os (23 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 631 once invoked, about $0.0001 per session on Opus 5.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-09-01.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…