
Product
Socket Now Protects the Microsoft Edge Extension Ecosystem
Enterprise security teams can now detect malware, credential theft, suspicious network activity, and risky updates across Microsoft Edge extensions.
@brickhouse-tech/sync-agents
Advanced tools
Simple scripts to DRY up common agent interactions across multiple LLM providers.
One .agents/ directory. Every AI coding assistant. Always in sync.
sync-agents is a package manager and sync engine for AI-agent context — the rules, skills, workflows, subagents, plans, specs, and ADRs you feed to Claude, Cursor, Windsurf, and Copilot. Write everything once in .agents/, and sync-agents fans it out to every tool via symlinks, keeps an AGENTS.md index current, and lets you pull shared context from other repos as safely and reproducibly as you'd install an npm package.
If you use more than one AI coding tool — or more than one repo — you already know the pain: the same rules copy-pasted into .claude/, .cursor/, .windsurf/, and .github/copilot/, drifting apart the moment you edit one of them. Team conventions living in a wiki nobody's agent reads. A "cool skill" pasted from the internet with zero review of what it actually tells your agent to do.
sync-agents fixes all three:
.agents/ is the single source of truth; tool directories are symlinks into it. Edit once, every tool sees it instantly.sources.yaml, get SHA-pinned, lockfile-verified installs — a package manager, not a copy-paste culture.Think of the instructions you give AI coding assistants as software. This tool is npm for your AI's brain.
.agents/) that holds everything you've taught your AI: house rules, reusable how-to guides, step-by-step playbooks.No more copy-pasting the same instructions into four different tools, and no more wondering where that one config file came from.
# npm — ships prebuilt native binaries, no Go toolchain needed
npm install -g @brickhouse-tech/sync-agents
# Homebrew
brew install brickhouse-tech/tap/sync-agents
# go install (Go 1.21+, no Node needed)
go install github.com/brickhouse-tech/sync-agents@latest
Pre-built archives (with SHA-256 checksums) are also on the Releases page. More detail in docs/install.md.
cd your-project
# 1. Create .agents/ (rules/, skills/, workflows/, STATE.md) + AGENTS.md index
sync-agents init
# 2. Add your first rule and skill
sync-agents add rule no-secrets
sync-agents add skill code-review
# 3. Fan everything out to .claude/, .windsurf/, .cursor/, .github/copilot/
sync-agents sync
# 4. Install a shared skill from another repo (SHA-pinned + scanned + quarantined)
sync-agents source add skill:anthropic/skill-pack@v1.2.0/skills/code-review
sync-agents quarantine # review the scan findings
sync-agents approve code-review # promote it into .agents/
# 5. Check that everything is wired up
sync-agents status
That's it — every supported tool now reads the same rules, and AGENTS.md (symlinked to CLAUDE.md) indexes it all automatically.
Rules, skills, workflows, subagents, plans, specs, and ADRs each get a first-class home under .agents/, routed to the right place per tool (ADRs even track proposed/accepted/denied status by directory). Topology →
sources.yaml + sources.lock: every upstream artifact resolves to a commit SHA, downloads are content-hashed, and a tampered tarball aborts before anything touches disk. pull, update, source list — reproducible like a real package manager. Sources →
Remote installs are treated like a hostile supply chain. Fetched artifacts are scanned for curl | bash patterns, credential-access-plus-network combos, obfuscation, and prompt injection — then held in .agents/.quarantine/ until you approve them. Quarantine →
npm link for agent context: point a source at a live local checkout instead of a frozen snapshot. Edits flow both ways, git pull reaps updates, and the link is recorded declaratively so it survives clones. Linked sources →
sync-agents lock writes agents.lock (provenance — where every rule, skill, hook, and spec came from) + agents.sum (go.sum-style content hashes for the whole tree). sync-agents verify then proves the tree is exactly what was reviewed — a post-install edit to a pulled artifact, an injected file that skipped quarantine, or a swapped symlink all fail verify --json with a non-zero exit. PLEX-style drift detection for your AI context. Integrity lock →
Drop rules into rules/macos/, rules/linux/, or rules/unix/ and they only sync on matching machines. One committed tree, no brew-rules noise on your Linux box. OS routing →
Every artifact is indexed into a generated AGENTS.md (symlinked to CLAUDE.md), with descriptions pulled from frontmatter, passive rules @-imported for Claude, and an ## Inherits section for org → team → project rule hierarchies. Index → · Inheritance →
sync-agents lint validates every SKILL.md against Claude's published authoring rules (name format, description quality, reserved words) and --fix mechanically repairs what it can. CI-friendly exit codes. Lint →
promote an artifact from a project to your user-level ~/.agents/, then global sync fans it out to every tool's user config dir with semantic-aware routing. Global commands →
The full manual lives in docs/:
.agents/ tree, config, STATE.mdMIT © Brickhouse Tech
FAQs
Simple scripts to DRY up common agent interactions across multiple LLM providers.
We found that @brickhouse-tech/sync-agents demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Product
Enterprise security teams can now detect malware, credential theft, suspicious network activity, and risky updates across Microsoft Edge extensions.

Research
/Security News
Socket researchers found 18 Chrome extensions and one Edge extension delivering a wallet drainer, credential theft, and other malicious payloads.

Product
Create ClickUp tasks from Socket alerts, automate ticketing with custom rules, and keep alert and task status synchronized.