aigent-OS gives Claude Code fully autonomous memory and context management. It remembers across sessions, checkpoints itself, and manages its own context window so you never re-brief it. A free, open-source operator layer, not a chat wrapper.
The day-one first-win menu. Three dead-simple, high-value tasks (two zero-dependency) that each put a real, usable artifact in the operator's hands in minutes, so the "ship something real" promise is met on day one and never waits on a connector or OAuth.
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Transform AI-generated documentation into human-readable prose with personality. USE WHEN: Converting rigid AI docs (checklist spam, CAPS LOCK emphasis, perfect symmetric structures, template dumps) into flowing, conversational writing that feels colleague-authored. Different from /humanizer — that skill detects AI…
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…
When the principal is in learning mode (reading a repo, watching a talk, processing a new tool), /learn takes a brief input and produces a structured note in vault/concepts/learning/ with category, modern-stack location, relevance verdict, and reconsideration triggers. Captures the value of every learning sweep…
Discovers missing honesty, trust-decay, failure-mode, and decision-outcome entries from local evidence; stages judgment and permits direct mutation only after an executable oracle.
The AIgent first-run operator-business interview. Learn the operator's business in three plain questions, write the first memory, and play back a briefing that reads personal, not templated. This is the "it remembers me" moment. A distinct skill that LAYERS ON TOP of the base /setup (which is left intact), it does not…
When the user (or an agent) is confused about where something lives, who owns what, what the rules are, or what to do next, run this to load the canonical map.
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports…
Lyra's spec-port skill. Takes a complete written specification and ports it into working code or a vault artifact. Confirms scope, reads the target, builds, returns honesty ledger.
Take a slice of the current conversation and promote it to a durable vault artifact — concept note, project update, person profile, or doctrine entry. Pairs with /close. /close writes the daily note (transient outcome record); /promote elevates specific insights to permanent vault content the framework can refer back…
Newton's multi-source deep research skill. Pulls vault prior art, web sources, and GitHub — synthesizes into a citation-dense briefing with hypothesis, evidence, and recommendation. Returns honesty ledger.
The resume verb, invoked explicitly — load the newest valid capsule by createdat, re-ground against live memory, then ACT on waitingon. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
SELF-CORRECT tool choice. About to Read a long file just to extract one piece of info? Use a sandbox tool that returns only the summary. About to run a long shell command? Same. Sandbox keeps raw output OUT of context — only summaries land. Triggers when about to flood context with large output.
Echo's vault traversal skill. Read-only graph walk — find all notes related to a topic, trace wikilink chains, inventory a directory, or spelunk a codebase for definitions and call chains.
Spawn a reviewer subagent with 4-6 specific verification questions before declaring non-trivial code work done. Triggers when changes are >30 LOC, multi-file, hot-path, prompt-affecting, or genuinely uncertain. Bad asks produce bad answers — this skill forces structured verification questions, not "is this good?".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: