Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/NoesisVision/nasde-toolkitnpx agentmods add skills/noesisvision/nasde-toolkit/nasde-benchmark-from-historyWrote 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/noesisvision/nasde-toolkit/nasde-benchmark-from-history)<a href="https://agentmods.dev/skills/noesisvision/nasde-toolkit/nasde-benchmark-from-history"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/nasde-benchmark-from-history/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/noesisvision/nasde-toolkit/nasde-benchmark-from-history"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/nasde-benchmark-from-history.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.00126 | $0.02902 |
| Opus 5 | $0.00063 | $0.01451 |
| Sonnet 5 | $0.00025 | $0.00580 |
| Haiku 4.5 | $0.00013 | $0.00290 |
Grade C, and why
nasde-benchmark-from-history scanned grade C with 2 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 11d 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 deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
RUN apt-get update && apt-get install -y git curl wget ca-certificates && rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
RUN apt-get update && apt-get install -y git curl wget ca-certificates && rm -rf /var/lib/apt/lists/* How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NASDE Benchmark from Git History
Generate NASDE benchmark tasks by mining git history. You analyze commits, diffs, and PR descriptions to identify self-contained changes that make good evaluation candidates, then generate task files with user approval.
Prerequisites
- A git repository with meaningful commit history (the repo you're currently in, or a path to another local repo)
- An existing NASDE benchmark project (run
nasde initfirst, or use thenasde-benchmark-creatorskill) - If the benchmark project doesn't exist yet, create it first — this skill generates tasks, not the project scaffold
Critical: line endings on Windows (read this first)
When generating tests/test.sh, solution/solve.sh, or environment/Dockerfile on a Windows host, write them with LF line endings or every trial fails with bash: required file not found (the kernel reads #!/bin/bash\r as the shebang). See the full explanation and .gitattributes template in the nasde-benchmark-creator skill.
Quick rules:
- The benchmark project MUST have a
.gitattributesenforcing*.sh text eol=lfandDockerfile text eol=lf.nasde initcreates this. If the existing project lacks it, create.gitattributesbefore generating any task files. - When writing files programmatically, use
path.write_text(content, encoding="utf-8", newline="")— never the bare default which translates\n→\r\non Windows. - Sanity-check after generation:
find tasks/<new-task> -name '*.sh' -o -name 'Dockerfile' | xargs file | grep CRLFshould print nothing.
Step 1: Identify the source repository and commit range
Ask the user:
- Which repository? Default: the current working directory. Can also be a path to another local repo.
- What commit range? Options:
- A branch name (analyze all commits on that branch)
- A commit range (
abc123..def456) - Last N commits (
HEAD~20..HEAD) - Specific PR numbers (if the repo has a GitHub remote, use
gh pr view) - "Just show me good candidates" — scan the last 50 commits and filter
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.
- 11d ago First seen · 308 lines · 126 tokens per session scan C 12de698c6ca6
nasde-benchmark-from-history is a skill published in the GitHub repository NoesisVision/nasde-toolkit (13 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 2,902 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
code-reviewer
Performs comprehensive code reviews with security, quality, and best practice checks.
generate-tests
Generate EvalView test cases — either from a SKILL.md file using LLM-powered generation, or by capturing real agent interactions through a proxy.
run-eval
Run EvalView regression checks against golden baselines to detect regressions in AI agent behavior after code, prompt, or model changes.
watch
Start EvalView watch mode to automatically re-run regression checks whenever project files change.
procrastination-buster
Beat procrastination with task breakdown, 2-minute starts, and accountability tracking.
code-reviewer
A skill that helps review code for best practices, bugs, and security issues.