Oh My Claudecode
Teams-first Multi-agent orchestration for Claude Code
Is Oh My Claudecode safe? Strong public trust posture, backed by multiple independent signals.
Compare Oh My Claudecode
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Oh My Claudecode scores 84.4/100 (Grade A), ranked #9 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.9/10; 32% of recent commits are signed; no published advisory affects its latest release (oh-my-claude-sisyphus); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How Oh My Claudecode could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 3.9 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dangerous-Workflow 0 +7.6 → 92.0 A · #2 of 371
- Sign every commit32% signed today +2.5 → 86.9 A · #7 of 371
Chain of custody
Scanners check what the code says. This traces who ships Oh My Claudecode and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.
-
Source Partly signed
github.com/Yeachan-Heo/oh-my-claudecode, MIT, last pushed 2026-10-10. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 6CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked and attested
- npm oh-my-claude-sisyphus Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: oh-my-claude-sisyphus 5.6.2. No published advisory affects it (OSV, checked 2026-10-10).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Oh My Claudecode’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.
How Oh My Claudecode compares in Agent Skills
- #7 MisakaNet 86.7 +2.3
- #8 Skill Scanner 85.2 +0.8
- #9 Oh My Claudecode 84.4 this agent
- #10 Obsidian Wiki 83.7 −0.7
- #11 Claudecodeui 83.7 −0.7
Bars show each HVTrust score; the tick marks Oh My Claudecode’s 84.4.
Where the 84.4 comes from
HVTrust dimensions vs the Agent Skills average
84.4 / 100 · 100.0% confidenceOh My Claudecode Agent Skills average (371 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.1 / 100Common questions about Oh My Claudecode
Does Oh My Claudecode publish package provenance?
Does Oh My Claudecode have an OpenSSF Scorecard?
Is Oh My Claudecode actively maintained?
What license does Oh My Claudecode use?
Are Oh My Claudecode's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Oh My Claudecode's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Oh My Claudecode?
For maintainers
HVTrust scores Oh My Claudecode from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/oh-my-claudecode)
<a href="https://hvtracker.net/agents/oh-my-claudecode"><img src="https://hvtracker.net/badge/oh-my-claudecode.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON