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.
npx skills add wefio/NodeMemoryGraph --skill repo-developmentgit clone --depth 1 https://github.com/wefio/NodeMemoryGraphWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wefio/nodememorygraph/repo-development)<a href="https://agentmods.dev/skills/wefio/nodememorygraph/repo-development"><img src="https://agentmods.dev/badge/skills/wefio/nodememorygraph/repo-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wefio/nodememorygraph/repo-development"><img src="https://agentmods.dev/badge/skills/wefio/nodememorygraph/repo-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.02983 |
| Opus 5.5 | $0.00013 | $0.01193 |
| Sonnet 5.5 | $0.00006 | $0.00597 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
repo-development 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 6d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository development
Keep the workflow small, evidence-based, and friendly to concurrent Agents. The code and logic should be easy to maintain. Complexity must be kept within a limit of 15.
Repository governance
- Treat the repository as the Agent's working environment. When a recurring task is hard to route or verify, improve its existing owner, route, or Skill instead of adding a private workaround or another source of truth.
- Treat an Agent completion claim as a proposal. Targeted tests, independent verification, clean CI, and—when the change crosses an external boundary—a real integration run determine whether the change holds. Each proof is scoped to what it actually measured.
- Move work, PRs, decisions, guardrails, and releases only through their explicit lifecycle operations. Do not infer a state transition from phrases such as "done" or "ship it" and do not bypass its prerequisites.
- Detect entropy aggressively: stale temporary work, expired guardrails, duplicate tests, unused compatibility layers, and superseded abstractions. Automatically remove only generated, cached, or explicitly expiring material; propose reviewable candidates before deleting source, history, public interfaces, issues, or pull requests.
- Keep the repository's spending bounded: never invoke live LLM, embedding, or full benchmark workloads unless the task explicitly calls for them.
- Keep one authoritative writer for each fact. Observe or reference GitHub, Contracts, repository state, verification receipts, and NMG memory through their owning interfaces rather than mirroring them into a competing store.
- In a shared or parallel-Agent worktree, isolate before you commit. Run
git status --shortfirst: other Agents' uncommitted changes, or a HEAD that moved under you, mean the tree is shared. Nevergit add -Aorgit commit -athere; stage only your owned paths. When the worktree is actively shared, prefer a dedicatedgit worktree addfor your change, commit only your files, and hand the shared tree back by reverting only your files to HEAD. A commit that silently swallows another Agent's working tree is a coordination failure, not a merge. When the change lands or is abandoned, remove the dedicated worktree and its branch (git worktree remove <path>thengit branch -D <name>) so used-up worktrees do not accumulate.
What ships with it
8 files beside SKILL.md 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.
- 6d ago Changed · +1 lines 9ec24ee0c5ad
- 10d ago Changed · +2 lines e9a90817185b
- 1mo ago Changed · -10 lines 464860f2d9a6
- 1mo ago Changed · +11 lines 566f8f72dff4
- 1mo ago Changed · +10 lines 0b6872b366c9
- 1mo ago Changed · +10 lines de232f718816
- 1mo ago Changed · +17 lines 0ed08d0f78d3
- 1mo ago Changed · +67 lines 7a7a881b1a71
- 2mo ago First seen · 95 lines · 32 tokens per session scan A 177265cd44d9
repo-development is a skill published in the GitHub repository wefio/NodeMemoryGraph (0 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 2,983 once invoked, about $0.0001 per session on Opus 5.5. 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 skills, from other repositories
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
github-auth
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
agency-jira-workflow-steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.