# Rune

> Registry manager for skills, agents, and rules. Keeps .claude/skills/, .claude/agents/, and .claude/rules/ synced with central registries. Run check after modifying files, sync at session start.

- **Type:** Skill
- **Install:** `agentstack add skill-nomograph-ai-rune-rune`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [nomograph-ai](https://agentstack.voostack.com/s/nomograph-ai)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [nomograph-ai](https://github.com/nomograph-ai)
- **Source:** https://github.com/nomograph-ai/rune
- **Website:** https://gitlab.com/nomograph/rune

## Install

```sh
agentstack add skill-nomograph-ai-rune-rune
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# rune -- registry manager

Manages skills, agents, and rules across projects via git-based registries.
Skills are markdown files in `.claude/skills/` that teach agents
how to perform workflows. Agents are subagent definitions in
`.claude/agents/`. Rules are conditional instructions in `.claude/rules/`.
rune keeps them current.

## When to invoke

- **After modifying any file in `.claude/skills/`, `.claude/agents/`, or
  `.claude/rules/`**: run `rune check` to detect drift. If drifted, ask
  the user if they want to push.
- **At session start**: muxr pre_create hook runs `rune sync` automatically.
  You do not need to run sync yourself.
- **When the user asks about skills**: run `rune ls` to show status.
- **When adding an item**: `rune add  --from  [-t type]`.

## Commands

```
rune check                    # show drift for all items
rune check --file PATH        # check a specific file (used by hook)
rune sync                     # pull updates from all registries
rune push               # push local changes back to registry
rune add  --from   # add a skill from a registry
rune add  -t agent      # add an agent
rune add  -t rule       # add a rule
rune ls                       # list items and sync status
rune init                     # create .claude/rune.toml for this project
rune setup                    # one-time: create config + install hook
```

## After modifying a skill file

The PostToolUse hook fires automatically and shows drift. When you
see drift output, present it to the user:

"I updated .md. It now differs from the  registry.
Want me to push this change upstream so other projects get it?"

Wait for explicit approval before running `rune push `.
This is an external write -- the same approval gate as git push.

## Output format

```
  tidy                     CURRENT                        registry: public
  voice                    DRIFTED  local is newer        registry: private
  mirror                   MISSING                        registry: public
```

- **CURRENT**: local matches registry
- **DRIFTED**: local and registry differ (direction shown)
- **MISSING**: in manifest but not on disk (run sync)
- **REGISTRY MISSING**: in manifest but not in registry

## Organizing an existing .claude/ directory with rune

If the user has skills, agents, or rules that are not yet managed by
rune, help them migrate:

1. Check if rune is set up: look for `.claude/rune.toml`. If missing,
   run `rune init`.
2. For each file in `.claude/skills/`, `.claude/agents/`, `.claude/rules/`:
   - If it came from a registry, add it to the manifest with
     `rune add  --from  [-t type]`.
   - If it was written locally and should be shared, suggest creating
     a registry (a git repo with `skills/`, `agents/`, `rules/` dirs)
     and using `rune push ` after adding it to the manifest.
3. Files in `.claude/commands/` should be moved to `.claude/skills/`.
   Claude Code merged commands into skills in v2.1.3. Move the file
   to a skill directory: `mkdir -p .claude/skills/` then
   `mv .claude/commands/.md .claude/skills//SKILL.md`.
4. Run `rune sync` to verify everything resolves.

## Configuration

- `~/.config/rune/config.toml` -- registries (name, url, branch)
- `.claude/rune.toml` -- per-project manifest (skills, agents, rules)

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [nomograph-ai](https://github.com/nomograph-ai)
- **Source:** [nomograph-ai/rune](https://github.com/nomograph-ai/rune)
- **License:** MIT
- **Homepage:** https://gitlab.com/nomograph/rune

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-nomograph-ai-rune-rune
- Seller: https://agentstack.voostack.com/s/nomograph-ai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.