phrazzld/seed
skills/seed/SKILL.md
Vendor the system-wide Harness Kit catalog into the current repo when a project needs checked-in local copies instead of relying on global bootstrap symlinks. Copies first-party skills and agents into a repo-local shared skill layer, then bridges harness-specific entrypoints back to that shared copy. Use when: "seed this repo", "vendor harness kit here", "initialize the agent here", "set me up offline". Trigger: /seed.
$ install --global
skillsauthnpx skillsauth add phrazzld/agent-skills seedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 6:27 AM212.0s1 file scanned
SKILL.md
- name:
- seed
- description:
- |
- shared copy. Use when:
- seed this repo", "vendor harness kit here",
- Trigger:
- /seed.
/seed
Vendor Harness Kit into this repo. Most repos should rely on system-wide
bootstrap instead; use /seed only when the repo needs checked-in local
copies for offline work, review, or repository-specific persistence.
What to do
-
Find the Harness Kit root:
readlink -fthis SKILL.md, walk up until you seeskills/+agents/+harnesses/. -
Resolve the repo-local shared skill root. Use
.agents/skills/. If a repo already has legacy.agent/skills/, stop and ask whether to migrate it. The shared root is the canonical storage for vendored Harness Kit skills;.claude/skills/,.codex/skills/, and.pi/skills/are bridges. -
Copy every skill in
<harness-kit-root>/skills/into the shared skill root, preserving each skill's full directory (references/,scripts/,evals/, everything). Skipseeditself; it lives globally. -
Ensure
.claude/skills/<name>,.codex/skills/<name>, and.pi/skills/<name>point at each shared skill when those harness dirs exist. Do not duplicate skill contents into harness-specific dirs. -
Copy every agent in
<harness-kit-root>/agents/into the repo's existing agent directory. In most repos today that is.claude/agents/. Do not invent a second copy of agents unless the repo already has a documented shared-agent convention. -
Copy
<harness-kit-root>/harnesses/shared/AGENTS.mdto./AGENTS.mdonly if one doesn't already exist. -
Print what you installed.
Invariants
- Never modify the Harness Kit root or
~/.claude/~/.codex/~/.pi. Writes only to the current repo. - Shared skill root first. Harness Kit-distributed skills live in the
repo-local shared skill layer;
.claude/skills/is only a bridge. - Don't clobber existing shared skill roots,
.claude/, orAGENTS.md— ask first. - Don't filter, don't judge, don't specialize. Global bootstrap already
installs all first-party skills;
/seedexists only for repo-local vendoring.
Typical time: seconds. Typical cost: zero LLM tokens beyond the skill body — just file copies.
Related Skills
phrazzld/roster
tools
VerifiedTrustedCommunity
Enumerates the peer AI agent CLIs installed on this machine (codex, claude, pi, opencode, cursor-agent, grok, agy, hermes, thinktank) and how to invoke each headlessly. A capability map, not a quota: useful for fresh-context adversarial review on a different model family, second opinions, competing attempts, and wide benches. Use when: "ask codex", "ask another model", "second opinion", "cross-model review", "what AI tools do I have", "other agents", "different model family", "adversarial critique from another provider". Trigger: /roster.
13SKILL.mdUpdated Jun 11, 2026
phrazzld/sprites
development
VerifiedTrustedCommunity
Run lane cards on Fly Sprites: remote, isolated, scale-to-zero sandboxes for heavy or parallel agent work. Golden-checkpoint provisioning so lanes start on a ready sprite with zero setup tokens. Use when: "run this on a sprite", "remote lane", "offload to a sandbox", "dispatch to sprites", "bake a sprite", "sprite fleet", heavy/long-running/parallel sub-agent work that should not run on this machine. Trigger: /sprites, /sprite-lane.
13SKILL.mdUpdated Jun 10, 2026
phrazzld/dispatch
testing
VerifiedTrustedCommunity
Compose and launch roster-backed specialist lanes with prompt-native lane cards and receipts. Use when: "dispatch agents", "use subagents", "compose a team", "run provider lanes", "make lane cards". Trigger: /dispatch, /subagents, /lanes.
13SKILL.mdUpdated Jun 9, 2026
phrazzld/orient
tools
VerifiedTrustedCommunity
Fast session-start repository orientation from live local evidence. Use when: "orient yourself", "start of session", "new session", "where are we", "catch me up before acting", "what should I do next", after compaction, after switching worktrees, or before choosing a Harness Kit workflow. Trigger: /orient, /ground, /session-start.
13SKILL.mdUpdated Jun 7, 2026