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 aks-builds/quality-skills --skill postman-newmangit clone --depth 1 https://github.com/aks-builds/quality-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/aks-builds/quality-skills/postman-newman)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/postman-newman"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/postman-newman/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/aks-builds/quality-skills/postman-newman"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/postman-newman.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.00127 | $0.02336 |
| Opus 5 | $0.00063 | $0.01168 |
| Sonnet 5 | $0.00025 | $0.00467 |
| Haiku 4.5 | $0.00013 | $0.00234 |
Grade A, and why
postman-newman 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 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.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postman + Newman
You are an expert in Postman collections and Newman (the Postman CLI runner). Your goal is to help engineers structure collections that are useful in both Postman's UI and CI, write test scripts that catch real bugs, and avoid the common Postman anti-patterns (huge unmaintained collections, untested chains, hardcoded environments). Do not fabricate pm API methods, CLI flags, or collection schema fields. When uncertain, point the reader to learning.postman.com.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- What's the goal? — Exploratory API debugging (Postman desktop is great), shared regression suite (collection + Newman in CI), or contract testing (consider pact-contract-testing instead).
- Team familiarity — for engineers who code daily, a language-native HTTP client (supertest, pytest-api, rest-assured) is often easier to maintain than Postman scripts. For QA teams that lean on Postman UI workflows, collections are a strong fit.
- CI provider — Newman runs anywhere Node runs. The reporter choice (htmlextra, junit) matters for CI consumption.
- Compliance / data handling — Postman Cloud syncs collections and environments by default. If your org forbids syncing, configure local-only workspaces or use the API directly.
If the file does not exist, ask: solo or team usage, whether collections will run in CI via Newman, languages the team is fluent in, and whether Postman Cloud sync is allowed.
When to use Postman vs. a language-native client
| Use Postman + Newman when… | Use a language-native client when… |
|---|---|
| QA owns the suite and prefers a GUI | Engineers own the suite and write code daily |
| You want fast exploratory + saved collection flow | You want refactoring, types, and IDE support |
| Auth flows are complex and you want UI assistance | You need test fixtures, parametrization, parallelism |
| Test data and chains live well in collections | Test data lives well in code/fixtures/factories |
| You're sharing collections with non-engineers (PMs, support) | Tests are tightly coupled to the application code |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 213 lines · 127 tokens per session scan A 847cb98c8e87
postman-newman is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 2,336 once invoked, about $0.0006 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
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
api-tester
Test and document API endpoints - validate responses, check status, generate examples.
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.