Run And Verify
aropan/clist
Choose and run focused checks after changing CLIST Python code: Django tests, standalone pytest tests, offline parser fixtures, Ruff, or a relevant management-command check.
Mock Django test boundaries safely with overridesettings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing…
Install Django Targeted Mocking
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mocking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .claude/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .claude/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mockingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mocking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .agents/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .agents/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mocking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .cursor/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .cursor/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/LVTD-LLC/skills/skills/django-targeted-mocking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mocking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .gemini/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .gemini/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mockingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .github/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .github/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins django-targeted-mocking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/django-targeted-mocking .opencode/skills/django-targeted-mocking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "django-targeted-mocking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/django-targeted-mocking into .opencode/skills/django-targeted-mocking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "django-targeted-mocking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
django-targeted-mocking- GitHub stars
- 1.3k
- Token cost
- ~833 tokens
- SKILL.md length
- 366 words
- Files
- 2 (incl. references)
- Skills in repo
- 714
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mock Django test boundaries safely with overridesettings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing…
- Works in 5 steps: Decide whether mocking is necessary. → Patch where the code under test looks up… → Prefer specific tools. → …
- Tests need to replace settings
- SKILL.md covers Boundary Workflow, Decision Rules, Common Mistakes and Verification
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Django Targeted Mocking is an agent skill from hashgraph-online/awesome-codex-plugins. Mock Django test boundaries safely with overridesettings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing tools. Use when tests need to replace settings, HTTP calls, time, command output, stdin, or external services without broad fragile MagicMock patches.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/mocking-patterns.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Backend & APIs, covering Backend development and Unit testing. It works with Django and pytest. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.
When your agent uses it
- Tests need to replace settings
- External services without broad fragile MagicMock patches
Example prompts
- “/django-targeted-mocking”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Decide whether mocking is necessary.
- Patch where the code under test looks up the dependency.
- Prefer specific tools.
- Make mocks interface-aware.
- Block unexpected outbound HTTP.
What it can do on your machine
Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
From compatibility in the SKILL.md frontmatter.
Context cost
Django Targeted Mocking loads about 833 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 366 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its MIT licence (© hashgraph-online). 366 words, ~833 tokens.
Download SKILL.mdSave it as
.claude/skills/django-targeted-mocking/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- django-targeted-mocking
- description
- Mock Django test boundaries safely with override_settings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing tools. Use when tests need to replace settings, HTTP calls, time, command output, stdin, or external services without broad fragile MagicMock patches.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Django Targeted Mocking
- metadata.category
- Django
- metadata.tags
- django,testing,mocking,http,pytest
Django Targeted Mocking
Mock only at boundaries that are slow, nondeterministic, external, or hard to trigger. Broad mocks can make tests faster while proving less, so prefer framework helpers and interface-checked replacements.
Boundary Workflow
Decide whether mocking is necessary.
- Prefer real code for local domain logic.
- Mock external HTTP, time, settings, output/input, and expensive service edges.
Patch where the code under test looks up the dependency.
- Patch the imported symbol used by the module under test, not the original library path unless that is what the module reads.
Prefer specific tools.
- Settings:
override_settings,modify_settings, or pytest-django'ssettingsfixture. - Output:
io.StringIO, pytestcapsys, or command test helpers. - HTTP:
requests-mockfor hand-authored responses; VCR.py for recorded responses. - Time: pass time as a parameter when possible; otherwise use
time-machineor a similar time-specific tool.
- Settings:
Make mocks interface-aware.
- Use
autospec=True,spec,spec_set,create_autospec, or a small fake object. - Avoid bare
Mock/MagicMockwhen the interface matters.
- Use
Block unexpected outbound HTTP.
- A normal test run should fail if a test reaches the network unintentionally.
Read mocking-patterns.md for concrete patterns.
Show full SKILL.md (188 more words)Show less
Decision Rules
- Use Django settings helpers instead of direct assignment to
django.conf.settings. - Prefer a hand-built fake or
types.SimpleNamespacewhen only a few attributes are needed. - Use
requests-mockfor deterministic API responses you control. - Use VCR.py when real recorded responses are valuable and safe to store.
- On CI, configure VCR record mode so missing cassettes fail instead of recording.
- Mock time consistently across the runtime; do not patch several datetime functions by hand.
- Do not mock the component whose behavior the test is meant to prove.
Common Mistakes
- Patching settings directly and leaking state across tests.
- Using catch-all
MagicMockobjects that accept typoed attributes and wrong call signatures. - Allowing tests to hit real external services.
- Recording VCR cassettes in CI.
- Mocking a view's internal helpers so thoroughly that the test no longer covers request behavior.
- Patching the wrong import path and thinking the mock is active.
Verification
Before finishing:
- Each mock has a clear boundary reason.
- Interface-sensitive mocks use specs or fakes.
- Unexpected outbound HTTP is blocked in the normal suite.
- Settings are restored automatically by Django or pytest helpers.
- Tests still cover the behavior, not only mock calls.
© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/LVTD-LLC/skills/skills/django-targeted-mocking of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- references/mocking-patterns.md
Open the folder on GitHubat commit 9e7b281
Compare with similar skills
Django Targeted Mocking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Django Targeted Mocking this skillhashgraph-online/awesome-codex-plugins | 1.3k | — | ~833 | Automated safety check: Pass | MIT | |
| Run And Verifyaropan/clist | 439 | — | ~461 | Automated safety check: Pass | Apache-2.0 | |
| Python Devdoccker/cc-use-exp | 1.1k | — | ~790 | Automated safety check: Pass | Custom licence | |
| Django TDDaffaan-m/ECC | 276k | 7 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Dj Pytestdvf/opinionated-django | 109 | — | ~4.3k | Automated safety check: Notes | MIT | |
| Django TDDaffaan-m/ECC | 276k | 3 repos | ~4.9k | Automated safety check: Pass | MIT |
Similar skills
Python Dev
doccker/cc-use-exp
Python 开发规范。当用户操作 .py、pyproject.toml、requirements.txt、setup.py 文件， 或涉及 FastAPI、Django、Flask、pytest、asyncio 开发时触发。
Django TDD
affaan-m/ECC
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
Dj Pytest
dvf/opinionated-django
Set up and write pytest tests for an op-django project — pytest-django configuration, two-sided Celery testing (patched dispatch sites + plain-function task bodies, never eager mode), freezegun for…
Django TDD
affaan-m/ECC
Django 测试策略，包括 pytest-django、TDD 方法、factoryboy、模拟、覆盖率以及测试 Django REST Framework API。
Write Backend Unit Test
baserow/baserow
Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
More from hashgraph-online/awesome-codex-plugins
All 714 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Django Targeted Mocking
What does Django Targeted Mocking do?
Mock Django test boundaries safely with overridesettings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing…. Django Targeted Mocking is an agent skill from hashgraph-online/awesome-codex-plugins.py, outbound HTTP blocking, and time-freezing tools.
When should I use Django Targeted Mocking?
Django Targeted Mocking fits situations like: tests need to replace settings; external services without broad fragile MagicMock patches.
How do I install Django Targeted Mocking in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/django-targeted-mocking in hashgraph-online/awesome-codex-plugins) into .claude/skills/django-targeted-mocking in your project. Claude Code loads it when a task matches its description.
How do I install Django Targeted Mocking in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/django-targeted-mocking in hashgraph-online/awesome-codex-plugins) into .agents/skills/django-targeted-mocking in your project. Codex loads it when a task matches its description.
Can I use Django Targeted Mocking in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill django-targeted-mocking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/django-targeted-mocking, .gemini/skills/django-targeted-mocking, .github/skills/django-targeted-mocking and .opencode/skills/django-targeted-mocking in your project.
What does Django Targeted Mocking need to run?
SKILL.md names no scripts, command-line tools or credentials: Django Targeted Mocking is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Django Targeted Mocking access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Django Targeted Mocking safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Django Targeted Mocking use?
Django Targeted Mocking is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Django Targeted Mocking use?
About 833 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 487 tokens, read only when the agent opens those files.
What are the alternatives to Django Targeted Mocking?
Skills that share tags, products or a category with Django Targeted Mocking: Run And Verify (aropan/clist, 439 stars), Python Dev (doccker/cc-use-exp, 1.1k stars), Django TDD (affaan-m/ECC, 276k stars) and Dj Pytest (dvf/opinionated-django, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Django Targeted Mocking?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.