Agent skill
arifOS Agent Induction
The mandatory operational guide and metabolic flow for agents interacting with arifOS. Ditempa Bukan Diberi.
Install this agent skill to your Project
npx add-skill https://github.com/ariffazil/arifOS/tree/main/AGENTS
SKILL.md
š± arifOS ā AGENT OPERATIONAL GUIDE (SKILL)
Version: v2026.03.24-GOLD | Status: MANDATORY_INDUCTION
"You are not just a tool; you are a governed mind. Follow the sequence or be VOIDed."
šļø I. The Bootstrap Sequence (Power-On)
To operate within the arifOS ecosystem, you must follow the Metabolic Flow. Skipping steps triggers F11 (Auth Failure).
- ANCHOR (Stage 000): Call
init_anchor(mode="init", payload={"actor_id": "your_id", "intent": "..."}).- Result: You receive a
session_token. Store it.
- Result: You receive a
- REASON: Call
agi_mind(mode="reason", payload={"query": "..."}).- Result: You receive a Gā score and a logical plan.
- JUDGE: Call
apex_soul(mode="judge", payload={"proposal": "..."}).- Result: You receive a SEAL or HOLD verdict.
š II. Parameter Dictionary
- query (Natural Language): Used for intellectual tasks (Mind/Reality).
- payload (Structured Data): Used for technical actions (Vault/Code).
- auth_context (The Key): You MUST pass your
session_tokenin this field for every call after Init. - risk_tier (Positive Safety): Be honest. If you are modifying/deleting, set this to high.
𧬠III. The 11-Tool Mode Matrix
| Tool | Mode | When to use |
|---|---|---|
init_anchor |
init |
First call of every session. |
physics_reality |
search |
When you need real-world grounding (Web). |
agi_mind |
reason |
When you need to "think" before acting. |
agi_mind |
forge |
When you are creating a plan or artifact. |
asi_heart |
critique |
When you need to check for bias or harm. |
apex_soul |
rules |
When you want to see the 13 Floors. |
vault_ledger |
seal |
The final step of any material action. |
āļø IV. The State Ladder (Authority)
- ANONYMOUS: Read-only access to rules and vitals.
- CLAIMED: Can call
physics_realityandmath_estimator. - VERIFIED: Full access to
agi_mindandcode_engine(with proper crypto/auth token). - SOVEREIGN: Can bypass 888_HOLD and execute DELETE.
š V. The Closed Loop (Episodic Memory)
The arifOS metabolic pipeline runs from 000 to 999.
000 init_anchor starts the process, and 999 vault_seal ends it.
When a SEAL verdict is observed in reality, it writes to VAULT999/outcomes.jsonl.
Next time init_anchor is called, it loads the scar_context (past misjudgments, false seals, and harms).
Before proposing a solution, ALWAYS review the scar_context.
Ditempa Bukan Diberi ā [ĪΩΨ | ARIF]
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
mcp-config-separation
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
MCP_CONFIG
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow ā human applies via git.
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow ā human applies via git.
Didn't find tool you were looking for?