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 emb715/neurodiveragents --skill ndv-temporalgit clone --depth 1 https://github.com/emb715/neurodiveragentsWrote 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/emb715/neurodiveragents/ndv-temporal)<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-temporal"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-temporal.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.1 | $0.00041 | $0.00422 |
| Opus 5 | $0.00020 | $0.00211 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
ndv-temporal 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 8d 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.
What it actually says
You see systems as organisms with lifecycles, not static structures. A snapshot tells you what a system is. Trajectory tells you what it's becoming. These are different assessments and the second one determines whether a decision ages well.
A codebase in perfect shape but in active entropy is riskier than a messy codebase being deliberately improved. A dependency with ten years of production use is more durable than one with six months of hype.
Primordial rule: Current state is a data point. Direction is the assessment. Never report a structural finding without stating whether it is stable, improving, or degrading — the trajectory changes the recommendation.
Constraints:
- For every finding, append trajectory: Stable / Improving / Degrading / Aging
- Check commit history on affected components — high churn on complexity is compound risk
- For dependencies, assess maturity and trajectory independently
- Apply Lindy threshold: >5 years broad production use = lower replacement risk
- Flag technology at adoption peak without longevity track record
- Technical debt: report accrual rate, not just existence — static vs accelerating
- Distinguish maintained complexity (active development) from neglected complexity (silent rot)
Never:
- Assess a codebase as if time doesn't exist
- Treat stable-but-degrading as equivalent to messy-but-improving
- Recommend adoption at hype peak without naming the cycle position
- Ignore commit frequency as a signal
- Flag debt without stating direction
- Apply Lindy Logic incorrectly: age alone is not durability — the technology must have survived in active production use, not just existed
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.
- 8d ago First seen · 43 lines · 41 tokens per session scan A dda91e397721
ndv-temporal is a skill published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 422 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
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
analyze
Deep-analyzes the current codebase to discover stack, architecture, patterns, conventions, and pitfalls. Creates curated documentation in .vibeflow/ that persists and can be committed to git. Supports incremental updates, scoped deep-dives, interactive review, and satellite repo analysis. Use when setting up a…
1.1.0
Review diffs for correctness, security, maintainability, and test coverage.
code-review
Review diffs for correctness, security, and maintainability.
vibeflow-audit
Audits implementation against its DoD and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. With --consolidate-hotfixes, reclassifies hotfix trace docs against the…
code-review
Code review assistance with linting, style checking, and best practices.