Claude-Code-Project-Structure-Learning-Repository: Skill for Claude Code

.claude/skills/testing/SKILL.md

testing is a skill for Claude Code from rohanmistry231/Claude-Code-Project-Structure-Learning-Repository. It costs 0 tokens per session (558 once invoked), scanned A, original, MIT.

A testing guide for a Blog API, using pytest and httpx. It explains where tests belong, how to use shared fixtures, and how to structure test steps.

In plain words
What is it for?
Use it to write, run, or repair Blog API tests and investigate test coverage.
Why use it?
It gives the agent project-specific rules, reducing misplaced tests and inconsistent setup when adding or fixing tests.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is rohanmistry231/Claude-Code-Project-Structure-Learning-Repository's own configuration. It tells Claude Code how to work on Claude-Code-Project-Structure-Learning-Repository itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Code-Project-Structure-Learning-Repository configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rohanmistry231/Claude-Code-Project-Structure-Learning-Repository. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rohanmistry231/Claude-Code-Project-Structure-Learning-Repository/main/.claude/skills/testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rohanmistry231/Claude-Code-Project-Structure-Learning-Repository

Made for: Claude Code.

Wrote 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.

agentmods badge for testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing/github.svg)](https://agentmods.dev/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing)
Your own site
<a href="https://agentmods.dev/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing"><img src="https://agentmods.dev/badge/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing/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.

agentmods 80×15 button for testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing"><img src="https://agentmods.dev/badge/skills/rohanmistry231/claude-code-project-structure-learning-repository/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00558
Opus 5.5 $0.00000 $0.00223
Sonnet 5.5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 2mo ago against content hash a1cd24c0e48d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing 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 2mo 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.

.claude/skills/testing/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Testing

Description

Write, run, or fix tests for the Blog API using pytest and httpx.

When to Use

Trigger this skill when the user says:

  • "write tests", "add tests", "test this"
  • "tests are failing", "fix the tests"
  • "what's the test coverage?"
  • "/test"

Instructions

When WRITING new tests

  1. Locate the correct test file. Tests live in arc/tests/. Match the source file:

    • arc/routes/posts.py → arc/tests/test_posts.py
    • arc/services/post_service.py → arc/tests/test_post_service.py
  2. Use the shared test fixtures from conftest.py. Never create a new database or app instance inline — use the fixtures:

    def test_something(client, db_session):
        ...
    
  3. Follow the Arrange / Act / Assert pattern.

    def test_create_post_returns_201(client):
        # Arrange
        payload = {"title": "Hello", "body": "World", "author_id": 1}
    
        # Act
        response = client.post("/posts", json=payload)
    
        # Assert
        assert response.status_code == 201
        assert response.json()["title"] == "Hello"
    
  4. Name tests descriptively. Format: test_<what>_<expected_result>

    • Good: test_get_post_returns_404_when_not_found
    • Bad: test_post, test_1
  5. Test the sad path too. For every happy-path test, add at least one test for the failure case (missing field, wrong type, unauthorized, not found).

When FIXING failing tests

  1. Read the full error output carefully before changing anything.
  2. Check if the test is wrong (asserting the wrong thing) or the code is wrong.
  3. If the schema or route signature changed, update the test to match — but note it in your reply.
  4. Never delete a test to make it pass.

When RUNNING tests

Run: pytest arc/tests/ -v --tb=short

For a single file: pytest arc/tests/test_posts.py -v

For coverage: pytest arc/tests/ --cov=arc --cov-report=term-missing

Output Format

When writing tests, show the complete test function(s), then say: "Run with: pytest arc/tests/<filename>.py::test_<name> -v"

Read the full file on GitHub · 73 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 73 lines · 0 tokens per session scan A a1cd24c0e48d

Subscribe to this mod's changes

testing is a skill published in the GitHub repository rohanmistry231/Claude-Code-Project-Structure-Learning-Repository (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 558 tokens. 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.

Related

Other skills, from other repositories

memstack-development-test-writer

Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.

cwinvestments/memstack · 70 tokens

verify

Runs this project's check chain through scripts/verify.py and reads the receipt it writes. Fires when tracked changes are finished, when the user asks whether work passes, before a commit, and before reporting a task done. Stays dormant in repositories with no detectable check chain, during read-only audits, and for…

cwinvestments/memstack · 71 tokens

memstack-development-webapp-testing

Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.

cwinvestments/memstack · 75 tokens

puppeteer-automation

Expert guidance for browser automation using Puppeteer with best practices for web scraping, testing, screenshot capture, and JavaScript execution in headless Chrome.

Mindrally/skills · 35 tokens

ros2-robotics

Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…

Mindrally/skills · 87 tokens

accessibility-a11y

WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.

travisjneuman/.claude · 26 tokens