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 n-n-code/n-n-code-skills --skill project-config-and-testsgit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/project-config-and-tests)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/project-config-and-tests"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/project-config-and-tests/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/n-n-code/n-n-code-skills/project-config-and-tests"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/project-config-and-tests.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.00037 | $0.00534 |
| Opus 5.5 | $0.00015 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
project-config-and-tests 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 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.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Config And Tests
This is a composable project overlay, not a standalone implementation workflow. Use it with matching language or discipline guidance when the main task is a configuration contract or deterministic tests at that boundary.
For review, inspect these contracts and report findings without editing config, tests, or process state. For implementation, apply only the requested changes and use isolated fixtures for validation.
When to use
The task involves configuration sources or precedence, defaults, parsing, normalization, path resolution, or deterministic tests around those seams.
Not for
Do not use this for general feature work (use the matching principle skill and
add project-core-dev only when repository-specific completion evidence is not
concrete), general test strategy (tester-mindset), framework-specific test
implementation, vendored dependency changes (project-vendor-boundary),
release-only work (project-release-maintainer), or environment diagnosis whose
cause has not been isolated (project-platform-diagnose).
Workflow
- Establish the contract before editing: sources, precedence, defaults, and the behavior of missing, empty, malformed, and unsupported values.
- Preserve help, version, and recovery paths when they can operate safely without valid config. Fail fast or fail closed when continuing would be unsafe or would silently apply misleading behavior.
- Separate pure parsing and normalization from environment, filesystem, and process-global lookup when the existing design permits it.
- Make tests independent of ambient environment, current directory, user home, wall-clock time, and shared filesystem state. Use the repo's fixtures and temporary-directory helpers, and clean up any remaining state.
- Cover precedence and representative missing, empty, invalid, override, relative, absolute, and platform-sensitive path cases that belong to the supported contract. Do not simulate unsupported platforms and present the result as observed evidence.
- Keep defaults, example config, help text, and documentation aligned. Avoid printing secret values in diagnostics or test output.
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 Changed · +4 lines 4c058446b382
- 1mo ago First seen · 53 lines · 37 tokens per session scan A 2dbd8aea40e2
project-config-and-tests is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 534 once invoked, about $0.0001 per session on Opus 5.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
verification-contract
Internal contract: the acceptance artifact per delivery unit — legacy (pre- feature 61) units may carry a frozen ACCEPTANCE.md (binding if present); post-feature 61 units use the unit doc's ## Acceptance criteria section as the canonical acceptance source; the unit doc's ## Evidence table serves as the execution…
test-go
Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
python-pytest-patterns
Modern pytest patterns for effective testing.
testing-patterns
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.
scenario-testing
This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.