Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add git-aditya-star/project-notesnpx agentmods add plugins/git-aditya-star/project-notes/marketplacegit clone --depth 1 https://github.com/git-aditya-star/project-notesGrade A, and why
project-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "project-notes",
"owner": {
"name": "aditya",
"email": "[email protected]"
},
"description": "Persistent per-project notebook plugins for Claude Code.",
"plugins": [
{
"name": "project-notes",
"source": "./",
"description": "Gives Claude a persistent, self-maintained notebook per project: distilled topic notes, a generated index injected into context each turn, and hooks that keep the notes current.",
"version": "0.2.1",
"license": "MIT",
"keywords": ["notes", "memory", "context", "notebook", "persistence"]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 19 lines scan A 2f91ca4001ac
project-notes is a plugin published in the GitHub repository git-aditya-star/project-notes (1 stars, last pushed 28d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
fable-orchestrator
Fable 5-first multi-agent orchestration for Claude Code: a token-frugal chair profile with tier routing (Sonnet 5 carries the volume, Opus 5 the hard slices), chair-sized effort per worker, a Requirements Ledger, guard hooks that enforce the discipline, and automatic teammate reaping. A clarification phase grills an…
orchestrator
Token-frugal multi-agent orchestration for Claude Code, built for a Claude Fable 5 chair: Fable plans and decides, Sonnet 5 carries the volume, Opus 5 takes the hard slices and escalations — each worker's effort sized by the chair — and a two-tier verification valve guards the close. When the Fable limit runs dry, an…
ballast
Builds up to a goal in a field you have no expertise in — learns the foundations it needs and keeps every solved path for the next goal.
paceflow
PACE workflow enforcement system — Plan-Artifact-Check-Execute-Verify-Review protocol with hooks.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
hipocampus
Persistent agent memory that survives across sessions — auto-compacting 3-tier memory with hybrid search. Your agent remembers what it learned, decided, and built.