andrewyng/context-hub

COLLECTIONcommunity
andrewyngMITUpdated 4mo agonpmGitHub

No description available.

Install the CLI and give your AI agent access to curated, versioned documentation. The CLI ships with a skill that teaches agents to fetch docs automatically instead of guessing from training data. Install it into your agent tool of choice: Copy the skill into your project: Or install it globally (applies to all projects): Copy the skill into your project's rules directory: The skill is a…

This collection bundles
11 skills

⚠ The trust score below reflects the installer package @aisuite/chub only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
14kGitHub stars
1kForks
4mo agoLast update
Package
Authorandrewyng
LicenseMIT
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.1.4 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

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

Tools

5 tools · none privileged
Statically extracted from the published packagev0.1.4 · 3mo 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.

chub_searchNo description published

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

chub_getNo description published

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

chub_listNo description published

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

chub_annotateNo description published

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

chub_feedbackNo description published

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

0 of 5 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

Install the CLI and give your AI agent access to curated, versioned documentation. The CLI ships with a skill that teaches agents to fetch docs automatically instead of guessing from training data. Install it into your agent tool of choice: Copy the skill into your project: Or install it globally (applies to all projects): Copy the skill into your project's rules directory: The skill is a standard markdown file at . Copy it to wherever your agent tool reads custom instructions from. For the…

Keywords
collection
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.