setup-shared-folder

A setup guide for syncing files between two computers through a private GitHub repository. It creates a shared folder with separate areas for project files, variants, and temporary work.

In plain words
What is it for?
Creating the repository and folder structure, pushing files from one computer, and cloning the shared files onto another.
Why use it?
It gives files from one machine a private, versioned place that another machine can clone and update, without using Dropbox, iCloud, or Google Drive.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/b1rdmania/ghostclaw/setup-shared-folder
Any agent
npx skills add b1rdmania/ghostclaw --skill setup-shared-folder
Clone the repo
git clone --depth 1 https://github.com/b1rdmania/ghostclaw

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00966
Opus 5 $0.00024 $0.00483
Sonnet 5 $0.00010 $0.00193
Haiku 4.5 $0.00005 $0.00097

Measured 2d ago against content hash 567bd7531029, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-shared-folder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/setup-shared-folder/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Setup Shared Folder

Creates a private GitHub repo for syncing files between the machine running GhostClaw and the user's primary machine.

Use when:

  • User wants files from GhostClaw accessible on another machine
  • User wants to avoid Dropbox/Google Drive/iCloud
  • User mentions "shared folder", "sync files", "access files on my laptop"

What it does

  1. Creates ~/ghostclaw-shared/ directory structure:

    • variant/ - Variant HTML/React exports
    • projects/ - Project files
    • scratch/ - Temp workspace
  2. Initializes git repo

  3. Creates private GitHub repo (under GhostClaw's GitHub account)

  4. Pushes initial commit

  5. Gives user clone instructions

Usage

# On GhostClaw's machine (already done by skill):
cd ~/ghostclaw-shared
# Repo created and pushed

# On user's machine (tell them to run):
git clone https://github.com/ziggythebot/ghostclaw-shared.git
cd ghostclaw-shared

Workflow after setup

When GhostClaw saves files:

# GhostClaw does this automatically:
cd ~/ghostclaw-shared
cp /path/to/file variant/
git add .
git commit -m "Add variant export"
git push

User gets files:

# User runs on their machine:
cd ~/ghostclaw-shared
git pull
# Files now available locally

Auto-sync option (optional)

For automatic pulling on user's machine:

# Add to crontab on user's machine:
*/5 * * * * cd ~/ghostclaw-shared && git pull -q

Implementation

#!/bin/bash

# Create directory structure
mkdir -p ~/ghostclaw-shared/{variant,projects,scratch}
cd ~/ghostclaw-shared

# Initialize git
git init
echo "# GhostClaw Shared Files

Synced workspace between GhostClaw and your main machine.

- \`variant/\` - Variant HTML/React exports
- \`projects/\` - Project files
- \`scratch/\` - Temp workspace

## Usage

Pull latest files:
\`\`\`
git pull
\`\`\`
" > README.md

git add .
git commit -m "Initial commit"

# Create private GitHub repo
gh repo create ghostclaw-shared --private --source=. --push

echo "✓ Shared folder created at ~/ghostclaw-shared"
echo "✓ GitHub repo: https://github.com/$(gh api user -q .login)/ghostclaw-shared"
echo ""
echo "On your main machine, run:"
echo "  git clone https://github.com/$(gh api user -q .login)/ghostclaw-shared.git"

Read the full file on GitHub · 151 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 151 lines · 48 tokens per session scan A 567bd7531029

Subscribe to this mod's changes

setup-shared-folder is a skill published in the GitHub repository b1rdmania/ghostclaw (91 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 966 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

lobu-operator

Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.

lobu-ai/lobu · 41 tokens

company-agent-infrastructure

Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…

lobu-ai/lobu · 70 tokens

lobu-builder

Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…

lobu-ai/lobu · 76 tokens

crm-ops

How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.

lobu-ai/lobu · 44 tokens

deliveroo-order

Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…

lobu-ai/lobu · 75 tokens

lobu

Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.

lobu-ai/lobu · 60 tokens