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 Yakoub-ai/neural-memory --skill neural-tasksgit clone --depth 1 https://github.com/Yakoub-ai/neural-memoryWrote 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/yakoub-ai/neural-memory/neural-tasks)<a href="https://agentmods.dev/skills/yakoub-ai/neural-memory/neural-tasks"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-tasks/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/yakoub-ai/neural-memory/neural-tasks"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-tasks.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.00040 | $0.01096 |
| Opus 5 | $0.00020 | $0.00548 |
| Sonnet 5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
neural-tasks 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neural Memory — Task Management
Manage tasks across their full lifecycle: new → in_progress → testing → done → auto-archived.
Tasks are first-class citizens in the knowledge graph: they link to code nodes via RELATES_TO edges, appear in every prompt via the context hook, and are auto-archived when done.
Task Statuses
| Status | Meaning |
|---|---|
new |
Alias for pending — task not yet started |
pending |
Task not yet started |
in_progress |
Actively being worked on |
testing |
Implementation done, under verification |
done |
Complete — will be auto-archived at session end |
List Tasks
Tool: neural_list_tasks
{}
Filter by status or priority:
Tool: neural_list_tasks
{ "status": "in_progress", "priority": "high" }
Include archived tasks:
Tool: neural_list_tasks
{ "include_archived": true }
Create a Task
Tool: neural_add_task
{
"title": "Implement caching for importance scores",
"phase_name": "Phase 3 — Performance",
"priority": "high",
"task_status": "in_progress",
"related_files": ["neural_memory/graph.py", "neural_memory/storage.py"]
}
Use task_status: "new" or "pending" for not-yet-started tasks.
Update a Task
Update by task name (substring match) or node ID:
Tool: neural_update_task
{ "title_or_id": "caching", "task_status": "testing" }
Update priority:
Tool: neural_update_task
{ "title_or_id": "caching", "priority": "high" }
Add related files:
Tool: neural_update_task
{
"title_or_id": "caching",
"task_status": "done",
"related_files": ["neural_memory/embeddings.py"]
}
Parameters
neural_list_tasks
| Parameter | Type | Default | Description |
|---|---|---|---|
status |
str | null |
Filter: pending, in_progress, testing, done |
priority |
str | null |
Filter: low, medium, high |
include_archived |
bool | false |
Include done/archived tasks |
project_root |
str | "." |
Project root |
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.
- 9d ago First seen · 126 lines · 40 tokens per session scan A 5aaa86d69918
neural-tasks is a skill published in the GitHub repository Yakoub-ai/neural-memory (1 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,096 once invoked, about $0.0002 per session on Opus 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
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).