Counterparty Channel Discipline
Keep agents quiet in shared channels: mention gating, silent observation, and a strict send policy so nothing internal ever leaks to outsiders.
- What
- Keep agents quiet in shared channels: mention gating, silent observation, and a strict send policy so nothing internal ever leaks to outsiders.
- Cost
- Free
- Needs
- Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me.
- Level
- Beginner — Pinned version: install the code at commit…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a written workflow contract for agents that sit in shared channels with external counterparties such as customers, suppliers, or partners. It keeps three things strictly separate: audience classification, participation consent, and permission to send. Default posture is require_mention in external groups, so the agent speaks only when explicitly addressed and stays silent otherwise; deliberate silence is a valid outcome. Reasoning, stack traces, secrets, host paths, and internal filing notices are never counterparty content. Prices, contractual language, legal matters, public posts, and unverified claims stay draft-only for operator approval. Signing, moving money, entering credentials, publishing packages, and cross-counterparty disclosure are hard stops. Output is re-checked after formatting, before every send, edit, or stream fragment. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is a written contract for the runtime that owns messaging, not an executable transport guard; enforcement depends on the owning runtime actually implementing the gates. A passing prompt test alone does not prove enforcement. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Counterparty Channel Discipline is a free Muse skill and written workflow contract for agents that sit in shared channels with external counterparties such as customers, suppliers or partners. It keeps audience classification, participation consent and permission to send strictly separate. The default posture is require-mention in external groups, so the agent speaks only when explicitly addressed.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Counterparty Channel Discipline" with your Muse. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/counterparty-channel-discipline/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Apply channel discipline to our agent in the #supplier channel" or "Review this agent's outbound policy for leaks." 3. Map the strict prompt template and the example channel policy to your own runtime's messaging contract; a passing prompt test alone does not prove enforcement. Tip: enable silent observation only with an explicit retention policy; observation is never permission to reply. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets, credentials, or internal traces into a shared channel, even while testing.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.