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 LambdaTest/agent-skills --skill newman-report-analyzergit clone --depth 1 https://github.com/LambdaTest/agent-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/lambdatest/agent-skills/newman-report-analyzer)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/newman-report-analyzer"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/newman-report-analyzer/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/lambdatest/agent-skills/newman-report-analyzer"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/newman-report-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00188 | $0.01739 |
| Opus 5 | $0.00094 | $0.00870 |
| Sonnet 5 | $0.00038 | $0.00348 |
| Haiku 4.5 | $0.00019 | $0.00174 |
Grade A, and why
newman-report-analyzer 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 13d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newman Report Analyzer
Analyze Newman run output in any format — terminal logs, JSON exports, JUnit XML — to give clear summaries, diagnose failures, spot slow requests, and recommend fixes.
Supported Input Formats
| Format | How to get it |
|---|---|
| Terminal (CLI) output | Copy/paste from terminal |
| JSON export | --reporter-json-export results.json |
| JUnit XML | --reporter-junit-export results.xml |
| HTMLextra data | User describes or pastes key sections |
Accept whichever format the user provides. Parse all available information.
What to Extract and Report
1. Run Summary
Always lead with the high-level outcome:
- Total requests run
- Total assertions (tests) run
- ✅ Passed / ❌ Failed counts
- Total run duration
- Any skipped requests
2. Failed Tests
For each failure, report:
- Request name and folder path
- The
pm.test()description that failed - Expected vs. actual (if available in output)
- HTTP status code received
- Response time
3. Request-Level Errors (non-test failures)
Newman can fail at the request level before tests even run:
- Connection errors — ECONNREFUSED, ENOTFOUND, ETIMEDOUT
- SSL errors — cert validation failures
- Redirect issues
- Script errors — syntax errors in pre-request or test scripts
Distinguish these from test assertion failures.
4. Slow Requests
Flag any request exceeding a reasonable threshold (default: 2000ms unless user specifies). Report:
- Request name
- Response time
- Whether a
--timeout-requestwould have killed it
5. Variable/Chaining Issues
Common symptom: a later request fails because a previous one didn't set an environment variable. Look for:
undefinedvalues in request URLs or bodies{{variable}}not replaced (appears literally in URLs)- Tests that set variables followed by tests that fail with unexpected nulls
Common Newman Error Patterns & Diagnoses
Error: ECONNREFUSED
Cause: The server isn't running or the wrong port/host is configured.
Fix: Check baseUrl environment variable. Confirm the server is up.
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.
- 13d ago First seen · 208 lines · 188 tokens per session scan A dd3a96b3c4ff
newman-report-analyzer is a skill published in the GitHub repository LambdaTest/agent-skills (367 stars, last pushed yesterday), licensed MIT. It adds 188 tokens to every session and 1,739 once invoked, about $0.0009 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-30.
Other skills, from other repositories
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
api-testing
API testing patterns for Playwright -- apiRequest fixture usage, Zod response schema creation and validation, test.step wrapping for multi-call tests, per-field negative/validation testing, path parameter fuzzing, and helper fixtures for shared setup/teardown. Use when writing or updating API test specs, adding tests…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
test-standards
Spec file conventions for the Playwright scaffold — imports from test-options.ts, test file structure (describe / beforeEach / test / test.step), single-tag rule, functional vs E2E vs API vs setup test types, data-driven test loops against TS static data, web-first assertions, destructive-test cleanup, and test…
data-strategy
Test data strategy for the Playwright scaffold — Faker + Zod factories for dynamic happy-path data, static TS files (.ts with as const exports — never .json) for domain-specific curated invalid sets, and the universal type-mismatch arrays in test-data/static/util/invalid-values.ts. Use when creating or editing a data…
helpers
Plain utility function conventions for the Playwright scaffold — app-specific helpers in helpers/{area}/ (authentication bootstrap, storage-state creation, data seeding) and generic utilities in helpers/util/ (date formatting, string manipulation, parsing). Use when adding a reusable function that does NOT need the…