Claude Code My Workflow

A ready-to-fork Claude Code template for academics using LaTeX/Beamer + R. Multi-agent review, quality gates, adversarial QA, and replication protocols.

Agent Skills HTML Listed MIT

Is Claude Code My Workflow safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.7 / 10
Provenance None
Signed commits 14%
Last push 21d ago
Compare Claude Code My Workflow
Suggest a correction

In detail: Claude Code My Workflow scores 56.2/100 (Grade C), ranked #154 of 385 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 14% of recent commits are signed; last pushed 2026-09-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Code My Workflow 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.

Chain of custody

Scanners check what the code says. This traces who ships Claude Code My Workflow and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/pedrohcgs/claude-code-my-workflow, MIT, last pushed 2026-09-27. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.7/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10
  3. Published packages None

    No registry package. Claude Code My Workflow is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Claude Code My Workflow’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 Claude Code My Workflow compares in Agent Skills

  1. #152 Happy 56.3 +0.1
  2. #153 Claude Council 56.2 ±0
  3. #154 Claude Code My Workflow 56.2 this agent
  4. #155 Distilly 56.2 ±0
  5. #156 Power Bi Agentic Development 56.2 ±0

Bars show each HVTrust score; the tick marks Claude Code My Workflow’s 56.2.

Where the 56.2 comes from

HVTrust dimensions vs the Agent Skills average

56.2 / 100 · 100.0% confidence

Claude Code My Workflow Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.8 / 25
in line with avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.2 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
14.6 / 20
0.6 above avg 14.0
AdoptionLog-scaled stars · package downloads
7.7 / 20
1.3 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-06
Rank Moved
Rank rose 31 spots (#169 → #138)
2026-09-27
Rank Moved
Rank rose 64 spots (#215 → #151)
2026-09-27
HVTrust Changed
HVTrust up 4.2pts (51.5 → 55.7)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
70.2
Activity sub-score · out of 100
#154

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed 21 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
1.7k
Forks
3.1k
Last Push
2026-09-27
21 days ago
Commits (4 wk)
9
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
=
was #154

Analysis

Activity Inputs

70.2 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
22.1 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
16.2 / 20

Common questions about Claude Code My Workflow

Claude Code My Workflow has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Claude Code My Workflow publish package provenance?
No published build provenance is currently detected for Claude Code My Workflow. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Claude Code My Workflow have an OpenSSF Scorecard?
Claude Code My Workflow has an OpenSSF Scorecard score of 5.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Claude Code My Workflow actively maintained?
Maintained. Last push was 21 days ago.
What license does Claude Code My Workflow use?
Claude Code My Workflow ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Code My Workflow's commits signed?
14% of the last 100 commits to Claude Code My Workflow are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
medium confidence
Implemented
Claude Code My Workflow appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Claude Code My Workflow'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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Claude Code My Workflow?

For maintainers

HVTrust scores Claude Code My Workflow 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
Rank 13Score 4HVTrust 4Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-06
Rank Moved
Rank rose 31 spots (#169 → #138)
2026-09-27
Rank Moved
Rank rose 64 spots (#215 → #151)
2026-09-27
HVTrust Changed
HVTrust up 4.2pts (51.5 → 55.7)
2026-09-27
Activity Score Changed
Activity score up 17pts (56 → 73)
2026-09-25
Rank Moved
Rank dropped 19 spots (#197 → #216)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 119 spots (#76 → #195)
2026-09-23
HVTrust Changed
HVTrust up 5.7pts (46.0 → 51.7)
2026-09-23
Activity Score Changed
Activity score down 18pts (74 → 56)
2026-09-22
Newly Listed
First tracked at rank #76
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#103 → #113)
2026-09-05
Rank Moved
Rank dropped 15 spots (#52 → #67)
2026-08-29
Scorecard Added
OSSF Scorecard: 5.7/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 117 spots (#155 → #38)
2026-08-29
HVTrust Changed
HVTrust up 35.7pts (25.9 → 61.6)
2026-08-28
Rank Moved
Rank dropped 25 spots (#130 → #155)
2026-08-27
Rank Moved
Rank dropped 21 spots (#109 → #130)
2026-08-26
Rank Moved
Rank dropped 64 spots (#45 → #109)
2026-08-23
Rank Moved
Rank rose 53 spots (#99 → #46)
2026-08-23
HVTrust Changed
HVTrust up 3.3pts (22.4 → 25.7)
2026-08-23
Activity Score Changed
Activity score up 20pts (60 → 81)
2026-08-21
Rank Moved
Rank rose 25 spots (#124 → #99)
2026-08-21
Activity Score Changed
Activity score up 10pts (50 → 60)
2026-08-16
Rank Moved
Rank dropped 12 spots (#111 → #123)
2026-08-11
Newly Listed
First tracked at rank #109

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/claude-code-my-workflow.svg)](https://hvtracker.net/agents/claude-code-my-workflow)
HTML:
<a href="https://hvtracker.net/agents/claude-code-my-workflow"><img src="https://hvtracker.net/badge/claude-code-my-workflow.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON