feat!: turn the skills repo into agent-env (m4rti.agents module) #2
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/agent-env"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The skills repo becomes the agent-env repo: one Home Manager module,
m4rti.agents, replacesm4rti-skillsand the scattered agent config in the NixOS repo.appsdecides which agents exist; every other part is installed into whichever enabled agents can take it.How each agent reads a secret (
envorheadersvalue{ file = ...; }) at startup:envheadersheadersHelperenv_http_headers+ codex wrapper{file:...}{file:...}!cat!catEvidence
nix flake checkcovered skill frontmatter and lint only; the module was never evaluated.After: new
subagentscheck (parses and renders all 10) andmodulecheck (full Home Manager evaluation, every part on, secret-backed stdio + HTTP MCP servers) ->all checks passed!headersHelperemits{"X-Api-Key": "<file contents>"}; the codex wrapper containsexport MCP_HTTP_SECRET_X_API_KEY="$(cat /run/secrets/key)"; read-only subagents render withsandbox_mode = "read-only"(codex),disallowedTools(Claude),tools: {...: false}(opencode), a reduced allowlist (pi).Merge Danger
Door: two-way
Nothing consumes this until the NixOS config is migrated; reverting the merge restores
m4rti-skills.Blast Radius: consumers
m4rti-skills.*is removed, so the NixOS config fails to evaluate on the nextnix flake update skillsuntil it moves tom4rti.agents. When migrating: drop theCODEX_HOMEsession variable (it would hide the Home Manager codex config), drop the separate zeit module import (this module imports it), and note Claude Code now defaults to the llm-agents build on every host.🤖 Generated with Claude Code