Agent skill · Content & Marketing

PheroPath

A filesystem-based stigmergy communication protocol. Use this to leave invisible "pheromones" (signals) on files to communicate context, risks, or status to other agents or your future self without modifying file content.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill pheropath --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/agent/pheropath/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PheroPath Agent Skill PheroPath allows you to attach context (DANGER, TODO, SAFE, INSIGHT) to files using Extended Attributes (or a sidecar fallback). ## Usage Guide ### 1. Secrete (Leave a Signal) **Script:** `scripts/secrete.py` **When to use:** - **DANGER**: You found a bug/risk you cannot fix immediately. - **TODO**: You are leaving untidied code or suggestions. - **SAFE**: You verified a module is robust. - **INSIGHT**: You want to explain *why* something is implemented this way. **Bash Examples (Few-Shot):** ```bash # Example 1: Mark a file as dangerous due to a race condition python3 scripts/secrete.py "src/concurrency.py" "DANGER" "Rate limit race condition under high load" --intensity 1.0 # Example 2: Leave a TODO note for refactoring python3 scripts/secrete.py "src/legacy_api.py" "TODO" "Needs migration to v2 API schema" # Example 3: Mark a test file as verified python3 scripts/secrete.py "tests/test_auth.py" "SAFE" "Passed all penetration tests" # Example 4: Add architectural insight python3 scripts/secrete.py "src/core/engine.py" "INSIGHT" "Core loop logic derived from paper X" --ttl 168 ``` ### 2. Sniff (Read Signals) **Script:** `scripts/sniff.py` **When to use:** -

What's inside
Steps it walks through
  1. Usage Guide
  2. 1. Secrete (Leave a Signal)
  3. 2. Sniff (Read Signals)
  4. 3. Cleanse (Remove Signals)
Ships with 1 file
  • metadata.json
Commands it runs
Example 1: Mark a file as dangerous due to a race condition
python3 scripts/secrete.py "src/concurrency.py" "DANGER" "Rate limit race condition under high load" --intensity 1.0
Example 2: Leave a TODO note for refactoring
python3 scripts/secrete.py "src/legacy_api.py" "TODO" "Needs migration to v2 API schema"
Example 3: Mark a test file as verified
python3 scripts/secrete.py "tests/test_auth.py" "SAFE" "Passed all penetration tests"
Example 4: Add architectural insight
python3 scripts/secrete.py "src/core/engine.py" "INSIGHT" "Core loop logic derived from paper X" --ttl 168
Example 1: Sniff a specific file
python3 scripts/sniff.py "src/main.py"
More from claude-skill-registry
All skills →
About this skill
What does the PheroPath skill do?

A filesystem-based stigmergy communication protocol. Use this to leave invisible "pheromones" (signals) on files to communicate context, risks, or status to other agents or your future self without modifying file content.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill pheropath --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going