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 agentmods add skills/neverinfamous/memory-journal-mcp/github-repo-setupnpx skills add neverinfamous/memory-journal-mcp --skill github-repo-setupgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/github-repo-setup)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/github-repo-setup"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/github-repo-setup.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.01838 |
| Opus 5 | $0.00026 | $0.00919 |
| Sonnet 5 | $0.00010 | $0.00368 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade C, and why
github-repo-setup scanned grade C with 1 finding 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 4d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Git CLI with SSH (`~/.ssh/id_ed25519`) How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository Setup
Scaffold a new public TypeScript/Node.js repo with community standards, CI, and strict tooling.
Prerequisites
- Git CLI with SSH (
~/.ssh/id_ed25519) - GitHub CLI (
gh) authenticated as{{ORG_NAME}} - Node.js 24+
- Default branch:
main - Credentials: Load from a secure environment file (e.g.,
{{SECRETS_ENV_PATH}}) or OS credential stores. CRITICAL: NEVER hardcode this path in shared templates or commit.envfiles.
Parameters
Replace these placeholders throughout:
| Placeholder | Example |
|---|---|
{{ORG_NAME}} |
neverinfamous |
{{REPO_NAME}} |
my-mcp-server |
{{DESCRIPTION}} |
MCP server for X |
{{YEAR}} |
2026 |
{{SECRETS_ENV_PATH}} |
C:\path\to\secrets.env |
1. Create Files (~28 total)
Read the reference file listed in the Template Source column for exact file contents. Files marked inline are defined directly below the table.
File Manifest
| File | Purpose | Template Source |
|---|---|---|
| Community Standards | ||
LICENSE |
MIT license | inline |
README.md |
Badges, quick start, TOC, examples | Adapt from reference repos |
CONTRIBUTING.md |
Fork → Clone → Branch → PR workflow | community-standards.md |
CODE_OF_CONDUCT.md |
Contributor Covenant 2.1 | community-standards.md |
SECURITY.md |
Vulnerability reporting process | community-standards.md |
CHANGELOG.md |
Keep a Changelog format (empty) | inline |
UNRELEASED.md |
SSoT for unreleased changes | inline |
| GitHub Automation | ||
.github/workflows/codeql.yml |
CodeQL static analysis | github-automation.md |
.github/workflows/lint-and-test.yml |
CI: lint, typecheck, build, test | github-automation.md |
.github/workflows/secrets-scanning.yml |
TruffleHog + Gitleaks | github-automation.md |
.github/workflows/dependabot-auto-merge.yml |
Auto-squash patch/minor PRs | github-automation.md |
.github/workflows/e2e.yml |
Playwright E2E tests | github-automation.md |
.github/dependabot.yml |
Grouped dependency updates | github-automation.md |
.github/ISSUE_TEMPLATE/bug_report.md |
Rich bug report template | github-automation.md |
.github/ISSUE_TEMPLATE/feature_request.md |
Feature request template | github-automation.md |
.github/ISSUE_TEMPLATE/config.yml |
Blank issue redirect | github-automation.md |
.github/pull_request_template.md |
Comprehensive PR checklist | github-automation.md |
| Project Config | ||
.gitignore |
Comprehensive ignores | inline |
.gitattributes |
Line ending normalization | inline |
.prettierrc |
Code formatting config | project-config.md |
.prettierignore |
Prettier exclusions | project-config.md |
.gitleaks.toml |
Secret scanning config | project-config.md |
package.json |
Project manifest | inline |
tsconfig.json |
TypeScript strict config | project-config.md |
eslint.config.js |
ESLint 10 strict + test config | project-config.md |
tsup.config.ts |
Build configuration | project-config.md |
vitest.config.ts |
Test configuration | project-config.md |
src/index.ts |
Entry point placeholder | Empty file |
What ships with it
4 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.
- 4d ago First seen · 137 lines · 51 tokens per session scan C a0ea640814e5
github-repo-setup is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,838 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
good-skill
Use only for fixture validation of narrow skill routing. Avoid for normal repo work.
broad-skill
Always use this skill for every task and all tasks.
faf-expert
Expert in the .faf format (Persistent Project Context for AI) and the faf-cli toolkit. Use when working with .faf files, scoring AI-readiness, syncing project context to CLAUDE.md, or discussing the Foundational Context Layer (FCL) doctrine. IANA-registered (application/vnd.faf+yaml). Anthropic-listed as "Persistent…
caveman-fixture
Always use caveman terse speech for every task.
skill-creator
Generate a new skill from a plain-language description — decides invocation control, arguments, and context cost, then scaffolds, validates, and tests it.
context-end
Close a workspace session by reviewing a proposed summary, recording approved outcomes, updating state and decisions, and checking repository safety. Use only when the user explicitly asks to end, close, or hand off the current session.