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 NoesisVision/nasde-toolkit --skill nasde-devgit clone --depth 1 https://github.com/NoesisVision/nasde-toolkitWrote 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-dev)<a href="https://agentmods.dev/skills/noesisvision/nasde-toolkit/nasde-dev"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/nasde-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/noesisvision/nasde-toolkit/nasde-dev"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/nasde-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 127 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Agent Snooping · line 81 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 82 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 83 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 97 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00103 | $0.01965 |
| Opus 5.5 | $0.00041 | $0.00786 |
| Sonnet 5.5 | $0.00021 | $0.00393 |
| Haiku 4.5 | $0.00010 | $0.00197 |
Grade A, and why
nasde-dev scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
After any run with `--with-opik`, verify that all feedback scores arrived in Opik. Use Python `urllib.request` (never curl — it drops the `Comet-Workspace` header): How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NASDE Toolkit Development
Internal guidelines for developing nasde-toolkit itself.
Important context:
nasde-toolkit/is the current production toolkit. The repository also containsSDLC/evals/which is the legacy predecessor — the original research/prototype that has been migrated into nasde-toolkit. Do NOT modifySDLC/evals/for new work. It will be removed once migration is confirmed complete.
Post-change verification protocol
After any significant change to the toolkit (new features, refactors, dependency updates, renamed identifiers), run the full verification pipeline before considering the work complete.
1. Quality gates (must pass before any commit/PR)
These are the same checks that run on CI. Always run locally before claiming code is ready:
# Lint
uv run ruff check src/ tests/
# Format
uv run ruff format --check src/ tests/
# Type check
uv run mypy src/nasde_toolkit/
# Unit tests
uv run pytest
All four must pass. If ruff format fails, run uv run ruff format src/ tests/ to auto-fix.
After pushing, verify CI passes on the PR with gh pr checks <PR_NUMBER>.
1b. Static checks
# No stale references to old names or patterns
grep -r "sdlc.eval\|sdlc-eval\|sdlc_eval" src/ docs/ CLAUDE.md README.md .claude/skills/ pyproject.toml --include="*.py" --include="*.md" --include="*.toml" --include="*.json" | grep -v __pycache__
# Package installs cleanly
uv sync
1c. Documentation and skills consistency
After any change to the evaluation pipeline, CLI flags, configuration schema, agent support, or sandbox/environment handling, update all of these:
Definition of done — CHANGELOG first. A feature/fix is NOT complete until it has an entry under
## [Unreleased]inCHANGELOG.md. Add it as part of the change (same PR), never "at release time" — leaving it for later means the Unreleased section silently drifts behind the merged PRs and release notes go out wrong. This has happened (the section fell 5 PRs behind before v0.5.0). When finishing any user-visible work, the last step before declaring done is: does[Unreleased]describe it, in the right section, with a[#NN]link-ref?
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 · 162 lines · 103 tokens per session scan A 1c26ee28fb16
nasde-dev is a skill published in the GitHub repository NoesisVision/nasde-toolkit (14 stars, last pushed 6d ago), licensed MIT. It adds 103 tokens to every session and 1,965 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (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.
uig
Build a User Input Grid (UIG) for an AI product or feature, evaluate existing eval datasets against it, and propose new inputs to fill coverage gaps. Use this skill whenever someone asks to design an eval framework, audit a test set, build a "user input grid", "synthetic query matrix" or "SQM", improve dataset…
eval-llm-judge
Write LLM-as-judge evaluator prompts for AI products. Use this skill whenever you need to evaluate semantic properties of AI outputs that cannot be checked programmatically — output quality, tone, factual accuracy, edge case handling, reference alignment. Also use when auditing existing judge prompts for bias…