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 neverinfamous/memory-journal-mcp --skill autonomous-devgit 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/autonomous-dev)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/autonomous-dev"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/autonomous-dev/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/neverinfamous/memory-journal-mcp/autonomous-dev"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/autonomous-dev.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.00058 | $0.00841 |
| Opus 5.5 | $0.00023 | $0.00336 |
| Sonnet 5.5 | $0.00012 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade B, and why
autonomous-dev scanned grade B 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 1mo 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Command Gates**: Do not execute destructive commands (`rm -rf`, `git reset --hard`) without explicit Human-in-the-Loop approval. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Development Workflow
This skill provides a deterministic software engineering harness, designed to wrap AI code generation with strict alignment gates, adversarial evaluations, CI/CD pipeline principles, and collaborative Git practices. Load this skill when designing or orchestrating multi-step architectural features, automating deployment workflows, or writing code inside a structured environment.
1. Project Alignment Gate (PROJECT.md)
Before beginning implementation, you MUST cross-reference the proposed feature against PROJECT.md at the repository root. If PROJECT.md is missing, ask the user to clarify the project goals or constraints before proceeding.
- In-Scope: Confirm the feature directly serves a goal in
PROJECT.md. Proceed. - Out-of-Scope: Hard block. Halt work immediately and inform the user.
- Constraints: Abide strictly by the constraints (language, architecture, dependencies) defined in the project file.
2. Security Safety Nets
- Execution Sandboxing: Never run unknown or unverified shell scripts directly. Execute isolated tasks within the
tmp/scratch directory. - Secret Protection: Check for exposed credentials or PII in diffs before committing. Never commit
.env. - Command Gates: Do not execute destructive commands (
rm -rf,git reset --hard) without explicit Human-in-the-Loop approval.
3. Generator / Evaluator Pipeline
Features cannot simply be written and committed. They must navigate a rigid pipeline based on the adversarial evaluation pattern:
- Research: Analyze local scope and external dependencies via parallel search strategies.
- Planning: Formulate architecture and acceptance criteria (generator).
- Acceptance Tests FIRST: Tests must be written before main implementation (TDD).
- Implementation: Produce code.
- HARD GATE: 0 test failures. You cannot proceed if tests fail. No stubs/placeholders allowed.
- Adversarial Review: Self-evaluate the code as a skeptical reviewer (evaluator). Actively search for edge cases, security vulnerabilities, efficiency loss, and anti-patterns.
- Documentation: Ensure docs stay tightly in sync with the codebase after the feature clears CI.
What ships with it
1 file 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.
- 1mo ago First seen · 80 lines · 58 tokens per session scan B dafabc7f3976
autonomous-dev is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 841 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
perf-profiling
Systematic performance profiling and optimization across frontend (Core Web Vitals, code splitting, lazy loading), backend (N+1 queries, async), and database (EXPLAIN ANALYZE, indexing) layers. Use when the user reports slow code, latency, memory leaks, needs to benchmark, or wants to speed up an application. Measure…
deep-debugging
Systematic debugging protocol for bugs that resist quick fixes. Use bisection, hypothesis trees, and scientific method when a bug isn't obvious from the stack trace. Goes beyond bugfix-quick for production-grade root cause analysis.
self-healing-orchestrator
Proposes patches for F2 (local-logic) and F3 (local-design) failures. NEVER applies without user approval. Confidence ≥0.7 to propose; below that, escalates raw findings. Counts toward replanbudget. Per-task: max 1; per-session: max 5.
failure-classifier
Classifies execution failures into F1-F5 (transient/local-logic/local-design/story-level/architectural). Outputs JSON with class, confidence, evidence, and recommended action. Deterministic rule-based classifier; no LLM call.
bugfix-quick
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.
problem-solving
5 techniques for different problem types. Use when stuck or facing complex challenges.