Is Token Optimizer safe to use?

Token Optimizer has an HVTrust score of 58.2/100 (Grade C), ranked #125 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Token Optimizer?

Token Optimizer scores 58.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.4k GitHub stars and is categorized under Agent Skills.

Token Optimizer

alexgreensh/token-optimizer

Find the ghost tokens. Fix them. Survive compaction. Avoid context quality decay.

Agent Skills Python Listed NOASSERTION

Is Token Optimizer safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 6%

Last push yesterday

Compare Token Optimizer

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Token Optimizer scores 58.2/100 (Grade C), ranked #125 of 351 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 4.2/10; 6% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Token Optimizer compares in Agent Skills

#123 Humanizer 58.2 ±0
#124 anti-slop 58.2 ±0
#125 Token Optimizer 58.2 this agent
#126 Claude Code Workflows 58.1 −0.1
#127 Claude Code Rails Upgrade Skill 57.9 −0.3

Bars show each HVTrust score; the tick marks Token Optimizer’s 58.2.

Where the 58.2 comes from

HVTrust dimensions vs the Agent Skills average

58.2 / 100 · 100.0% confidence

Token Optimizer Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.6 / 25

2.5 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

5.7 above avg 14.2

AdoptionLog-scaled stars · package downloads

8.1 / 20

0.9 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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/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.

Compare with another agent Get email alerts for Token Optimizer View Agent Skills Report missing data

80.8

Activity sub-score · out of 100

#125

In Agent Skills

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

2.4k

Forks

184

Last Push

2026-09-25

yesterday

Commits (4 wk)

347

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #121

Analysis

Activity Inputs

80.8 / 100

StarsRepository reach

20.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

10.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

of last 100 commits verified

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 9

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Token Optimizer

Token Optimizer 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 Token Optimizer publish package provenance?

No published build provenance is currently detected for Token Optimizer. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Token Optimizer have an OpenSSF Scorecard?

Token Optimizer has an OpenSSF Scorecard score of 4.2/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 Token Optimizer actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Token Optimizer use?

Token Optimizer ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Token Optimizer's commits signed?

6% of the last 100 commits to Token Optimizer 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

Token Optimizer appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Token Optimizer'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Token Optimizer?

For maintainers

HVTrust scores Token Optimizer 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

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 49 spots (#62 → #111)

2026-09-23

HVTrust Changed

HVTrust up 11.3pts (47.2 → 58.5)

2026-09-22

Newly Listed

First tracked at rank #62

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Scorecard Added

OSSF Scorecard: 4.1/10

2026-09-15

Grade Changed

Trust grade D → C

2026-09-15

Rank Moved

Rank rose 226 spots (#345 → #119)

2026-09-15

HVTrust Changed

HVTrust up 32.2pts (25.5 → 57.7)

2026-09-11

Rank Moved

Rank dropped 10 spots (#331 → #341)

2026-09-05

Rank Moved

Rank dropped 10 spots (#294 → #304)

2026-09-03

Rank Moved

Rank dropped 16 spots (#271 → #287)

2026-09-02

Rank Moved

Rank dropped 11 spots (#260 → #271)

2026-09-01

Rank Moved

Rank dropped 12 spots (#248 → #260)

2026-08-31

Rank Moved

Rank dropped 16 spots (#232 → #248)

2026-08-30

Rank Moved

Rank dropped 35 spots (#197 → #232)

2026-08-29

Rank Moved

Rank dropped 35 spots (#162 → #197)

2026-08-28

Rank Moved

Rank dropped 23 spots (#139 → #162)

2026-08-27

Rank Moved

Rank dropped 22 spots (#117 → #139)

2026-08-26

Rank Moved

Rank dropped 67 spots (#50 → #117)

2026-08-11

Newly Listed

First tracked at rank #50

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/token-optimizer.svg)](https://hvtracker.net/agents/token-optimizer)
            
HTML:
            <a href="https://hvtracker.net/agents/token-optimizer"><img src="https://hvtracker.net/badge/token-optimizer.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.3 · Raw JSON