brickhouse-tech · nmccready · Mar 14, 2026 · Mar 14, 2026
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Brickhouse Tech
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -1,11 +1,13 @@
 # sync-agents
 
-One set of agent rules to rule them all. `sync-agents` keeps your AI coding agent configurations in a single `.agents/` directory and syncs them to agent-specific directories (`.claude/`, `.windsurf/`) via symlinks. This ensures all agents follow the same rules, skills, and workflows without duplicating files.
+One set of agent rules to rule them all. `sync-agents` keeps your AI coding agent configurations in a single `.agents/` directory and syncs them to agent-specific directories (`.claude/`, `.windsurf/`, `.cursor/`, `.github/copilot/`) via symlinks. This ensures all agents follow the same rules, skills, and workflows without duplicating files.
 
 AGENTS.md serves as an auto-generated index of everything in `.agents/` and is symlinked to CLAUDE.md for Claude compatibility.
 
 ## Installation
 
+### npm
+
 ```bash
 npm install @brickhouse-tech/sync-agents
 ```
@@ -16,6 +18,13 @@ or globally:
 npm install -g @brickhouse-tech/sync-agents
 ```
 
+### Standalone (no npm required)
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/brickhouse-tech/sync-agents/main/src/sh/sync-agents.sh -o /usr/local/bin/sync-agents
+chmod +x /usr/local/bin/sync-agents
+```
+
 ## Topology
 
 `.agents/` is the source of truth. It contains all rules, skills, workflows, and state for your agents:
@@ -37,7 +46,7 @@ npm install -g @brickhouse-tech/sync-agents
   └── STATE.md
 ```
 
-Running `sync-agents sync` creates symlinks from `.agents/` subdirectories into `.claude/` and `.windsurf/`. Any changes to `.agents/` are automatically reflected in the target directories because they are symlinks, not copies.
+Running `sync-agents sync` creates symlinks from `.agents/` subdirectories into `.claude/`, `.windsurf/`, `.cursor/`, and `.github/copilot/`. Any changes to `.agents/` are automatically reflected in the target directories because they are symlinks, not copies.
 
 AGENTS.md is also symlinked to CLAUDE.md so that Claude reads the index natively.
 
@@ -50,7 +59,10 @@ AGENTS.md is also symlinked to CLAUDE.md so that Claude reads the index natively
 | Command | Description |
 |---|---|
 | `init` | Initialize the `.agents/` directory structure with `rules/`, `skills/`, `workflows/`, `STATE.md`, and generate `AGENTS.md` |
-| `sync` | Create symlinks from `.agents/` into `.claude/` and `.windsurf/`, and symlink `AGENTS.md` to `CLAUDE.md` |
+| `sync` | Create symlinks from `.agents/` into all target directories, and symlink `AGENTS.md` to `CLAUDE.md` |
+| `watch` | Watch `.agents/` for changes and auto-regenerate `AGENTS.md` |
+| `import <url>` | Import a rule/skill/workflow from a URL |
+| `hook` | Install a pre-commit git hook for auto-sync |
 | `status` | Show the current sync status of all targets and symlinks |
 | `add <type> <name>` | Add a new rule, skill, or workflow from a template (type is `rule`, `skill`, or `workflow`) |
 | `index` | Regenerate `AGENTS.md` by scanning the contents of `.agents/` |
@@ -63,7 +75,7 @@ AGENTS.md is also symlinked to CLAUDE.md so that Claude reads the index natively
 | `-h`, `--help` | Show help message |
 | `-v`, `--version` | Show version |
 | `-d`, `--dir <path>` | Set project root directory (default: current directory) |
-| `--targets <list>` | Comma-separated list of sync targets (default: `claude,windsurf`) |
+| `--targets <list>` | Comma-separated list of sync targets (default: `claude,windsurf,cursor,copilot`) |
 | `--dry-run` | Show what would be done without making changes |
 | `--force` | Overwrite existing files and symlinks |
 

diff --git a/src/md/SKILL_TEMPLATE.md b/src/md/SKILL_TEMPLATE.md
@@ -0,0 +1,23 @@
+---
+trigger: always_on
+---
+
+# ${NAME}
+
+## Description
+
+Brief description of what this skill enables.
+
+## Usage
+
+When to use this skill and how to invoke it.
+
+## Examples
+
+```
+Example usage or invocation here.
+```
+
+## Notes
+
+Any caveats, prerequisites, or related skills.
diff --git a/src/md/STATE_TEMPLATE.md b/src/md/STATE_TEMPLATE.md
@@ -1,42 +1,16 @@
-
 ---
 trigger: always_on
 ---
 
 # State
 
-This is the state template for sync-agents. It is used to define the state of the agent and its environment. The state markdown file itself is a human readble source for the agent to read and understand its current situation. It can be used to track the progress of the agent, identify any issues or challenges it may be facing, and provide a clear overview of its goals and objectives. The state is an important tool for the agent to use in order to make informed decisions and take appropriate actions to achieve its goals. By maintaining an up-to-date state, the agent can continuously learn and evolve, becoming more effective and efficient in its tasks.
-
-The goal is to improve the performance of the agent by providing it with a clear and structured representation of its current situation. This allows the agent to make informed decisions and take appropriate actions to achieve its goals. The state is also used to track the progress of the agent and identify any issues or areas for improvement. By maintaining an up-to-date state, the agent can continuously learn and evolve, becoming more effective and efficient in its xtasks.
-
-## TRACKING Agent State
-
-Every state tracking will begin with a header of `### YYYYMMDDHHMMSS STATE: <STATE_NAME or OBJECTIVE` followed by a description of the state, any relevant information about the agent's performance, issues, or updates, and any actions taken or planned to address the current state. This format allows for easy tracking and monitoring of the agent's progress over time, as well as providing a clear record of the agent's history and development. By maintaining a detailed and organized state history, the agent can learn from past experiences and make informed decisions to improve its performance in the future.> 
-
-The format above will be written below the `## STATE HISTORY BELOW` header in the STATE.md file. This allows for easy tracking and monitoring of the agent's progress over time, as well as providing a clear record of the agent's history and development. By maintaining a detailed and organized state history, the agent can learn from past experiences and make informed decisions to improve its performance in the future.
-
-## Formatted Agent State
+Track project progress, current objectives, and resumption context.
+Update this file regularly so agents can pick up where they left off.
 
-The formatted agent state will be a structured representation of the agent's current situation, including its goals, objectives, performance metrics, and any relevant information about its environment. This formatted state will be used by the agent to make informed decisions and take appropriate actions to achieve its goals. By maintaining an up-to-date and well-structured formatted state, the agent can continuously learn and evolve, becoming more effective and efficient in its tasks. The formatted state will also be used to track the progress of the agent and identify any issues or areas for improvement, allowing for continuous optimization of the agent's performance.
+## Format
 
-Example:
+### YYYYMMDDHHMMSS STATE: <objective>
 
-The state is structured as follows:
-
-```json
-{
-  "agent_name": "string",
-  "goals": ["string"],
-  "skills": ["string"],
-  "workflows": ["string"],
-  "issues": ["string"],
-  "last_updated": "timestamp"
-}
-```
-to `.agents/state.json`
+Description of current state, progress, blockers, and next steps.
 
 ## STATE HISTORY BELOW
-
-
-
-
diff --git a/src/md/WORKFLOW_TEMPLATE.md b/src/md/WORKFLOW_TEMPLATE.md
@@ -0,0 +1,24 @@
+---
+trigger: always_on
+---
+
+# ${NAME}
+
+## Trigger
+
+Describe when this workflow should be activated.
+
+## Steps
+
+1. Step one
+2. Step two
+3. Step three
+
+## Conditions
+
+- Pre-conditions that must be met
+- Any guards or checks
+
+## Output
+
+What the workflow produces or changes when complete.