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/ai-swiss/base/understand-statenpx skills add ai-swiss/base --skill understand-stategit clone --depth 1 https://github.com/ai-swiss/baseWrote 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/ai-swiss/base/understand-state)<a href="https://agentmods.dev/skills/ai-swiss/base/understand-state"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/understand-state.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.1 | $0.00040 | $0.00610 |
| Opus 5 | $0.00020 | $0.00305 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
understand-state 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 5d 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.
What it actually says
Understand the state
Orient before touching anything. The reading order is fixed: specs/ first, then the code,
never a plan or a review (see specs/current/00_overview/les-deux-plans.md).
Steps
- Read the truth plane. Open
specs/current/10_core/requirements.md(the ID index) and the chapter leaf for the area in question. This is what BASE requires. - Read the proof. Open
specs/current/10_core/requirements-matrix.md(generated). The✅/⚠️/❌column tells you which requirements are proven, weakly proven, or unproven. Runnpm run spec:matrixto regenerate it if in doubt. - Read the change plane. Skim
decisions/index.mdfor the durable choices and any open change record. This is why things are the way they are. - Confirm against the code. For a behaviour, read the function named normative in the leaf; the regeneration bar is: could the code be rebuilt from the spec plus its tests?
- Report the state and the next step. Name what is solid, what is
⚠️/❌, and the single most valuable next change. Hand off toplan(consequential) orimplement(obvious).
What you never do
- Treat a plan or a review as current truth.
- Invent a state you did not read; cite
file:lineor command output. - Drift into auditing a user's BASE project — that is a different agent.
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.
- 5d ago First seen · 51 lines · 40 tokens per session scan A 9910eecd2cdb
understand-state is a skill published in the GitHub repository ai-swiss/base (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 610 once invoked, about $0.0002 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-30.
Other skills, from other repositories
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.
implementing-iso-27001-information-security-management
ISO/IEC 27001:2022 is the international standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This skill covers the complete.
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.12.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
TRX Staking & SR Voting
Stake TRX, vote for Super Representatives, and claim voting rewards on TRON.