affaan-m/ECC

Name: affaan-m/ECC
Author: affaan-m

COLLECTIONattested

v2.0.0affaan-mMITUpdated 3mo agonpm GitHub

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

This collection bundles

868 skills303 agents1 MCP server414 commands

⚠ The trust score below reflects the installer package ecc-universal only. The bundled units are not individually verified or scanned — review them before use.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

3kDownloads/wk

215kGitHub stars

33kForks

3mo agoLast update

Package

Authoraffaan-m

LicenseMIT

Version2.0.0

Sourcegithub

npmecc-universal

GitHubaffaan-m/ECC

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 5eddf1a

Dependencies✓ 9 resolved · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv2.2.0 · 1mo agoHow well does this scan work?

CODE…ib/resolve-ecc-root.jsDynamic require of a computed module name

EvalsNone

IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev2.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

memory_saveNo description published

This tool published no description. Forge does not invent one.

memory_searchNo description published

This tool published no description. Forge does not invent one.

memory_readRead one ECC memory and its derived backlinks by stable memory ID.

Read one ECC memory and its derived backlinks by stable memory ID.

No input schema was published for this tool.

memory_doctorNo description published

This tool published no description. Forge does not invent one.

1 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

ai-agentsanthropicclaudeclaude-codedeveloper-toolsllmmcpproductivitycollection

Alternatives

Comparing tool surfaces…

affaan-m/ECC

Tools

Tools exposed

Dependency tree