skills.rest
open-mercato
open-mercatoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-share-this-session

Sanitize and publish a coding-agent session export with generated files to a public GitHub issue.

1.7k|382|Updated Sep 10, 2025
Search Tags:#sanitization#Privacy#CODEX#session sharing#consent gate#GitHub issue#harness feedback
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-share-this-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-share-this-session
Source: https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/om-share-this-session
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-share-this-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Sharing a coding-agent session for harness feedback normally risks leaking secrets, personal data, or customer information, and manually assembling a complete, auditable report is error-prone. This Skill builds a sanitized, consent-gated support bundle so maintainers can diagnose agent behavior without exposing private data.

Core Features & Use Cases

  • Complete session export handling: Accepts a native JSON session export or retrieves an explicitly identified active Codex thread via a bundled read-only exporter, verifying first and latest turn coverage.
  • Local sanitization pipeline: The prepare-share-bundle.mjs script redacts credentials, tokens, emails, IPs, phone numbers, private keys, and absolute paths, then produces a sanitized session.json, a ZIP of session-generated files, a manifest with SHA-256 hashes, and a privacy report.
  • Hard consent gate and atomic publication: Nothing is published until the user reviews the exact artifacts and types an explicit acknowledgement; publication then creates a deduplicated public branch and an upstream harness-feedback issue, with rollback if issue creation fails.
  • Use Case: After a coding agent hits a rate limit or produces a broken feature, you say "share this session" to file a complete, privacy-reviewed diagnostic report with the Open Mercato maintainers.

Quick Start

Ask the agent to share this session under a public slug like "share this session as login-flow-bug" and follow the review and consent prompts.

Frequently Asked Questions about om-share-this-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share a coding agent session for feedback?▼

Invoke the skill with a public kebab-case share name, for example "share this session as my-bug-report". It prepares a sanitized local bundle, shows you a full preview, and publishes only after you type the exact consent acknowledgement.

How does the session sanitizer remove secrets and personal data?▼

The prepare-share-bundle.mjs script redacts tokens, private keys, authorization headers, emails, IPs, phone numbers, and absolute paths using pattern rules plus high-entropy detection. A mandatory manual semantic review of every turn and file follows, since automated scanning is not a privacy guarantee.

Can I share a Codex session without a manual JSON export?▼

Yes, when trusted harness metadata provides the active Codex thread ID, the bundled export-codex-session.mjs helper reads the thread from the local Codex app-server over stdio. It never resumes, mutates, or publishes the thread, and fails closed if the export is unavailable.

What gets published when I share a session?▼

Exactly four artifacts go to a temporary public branch: sanitized session.json, generated-files.zip, manifest.json, and privacy-report.json, followed by a harness-feedback issue in open-mercato/open-mercato. The original export, redaction lists, and local review tree are never uploaded.

Can I share a session automatically without consent?▼

No. The skill has a hard interactive consent gate requiring the exact phrase "I AGREE TO PUBLICLY SHARE \"<name>\" WITH OPEN-MERCATO" after reviewing final artifact hashes. Any bundle regeneration invalidates prior consent and triggers a new preview.

What happens if issue creation fails after the branch is published?▼

The skill immediately invokes the delete-session-share operation to remove the just-created branch. If deletion also fails, it stops and prominently reports the exposed branch URL so a maintainer can remove it manually.

Related Skills

Explore More Software Engineering Skills→
stevengonsalvezstevengonsalvez

swarm-orchestration

Coordinate distributed Claude Code agents in isolated tmux sessions with file-based messaging.

Community
Advanced
sseshachalasseshachala

evidence-hygiene

Redact cookies and PII from bug-bounty screenshots, HAR files, and transcripts.

Community
Intermediate
managedcodemanagedcode
4

mcaf-solution-governance

Create and update AGENTS.md governance files for MCAF repositories.

Official
Advanced
8Dionysus8Dionysus
4

aoa-sanitized-share

Redact sensitive details from technical material and place sanitized output in a public-safe location.

Community
Intermediate