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 marlonvidal/tech-manager-os --skill bmad-teach-me-testinggit clone --depth 1 https://github.com/marlonvidal/tech-manager-osWrote 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/marlonvidal/tech-manager-os/bmad-teach-me-testing)<a href="https://agentmods.dev/skills/marlonvidal/tech-manager-os/bmad-teach-me-testing"><img src="https://agentmods.dev/badge/skills/marlonvidal/tech-manager-os/bmad-teach-me-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.
<a href="https://agentmods.dev/skills/marlonvidal/tech-manager-os/bmad-teach-me-testing"><img src="https://agentmods.dev/badge/skills/marlonvidal/tech-manager-os/bmad-teach-me-testing.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.00032 | $0.01512 |
| Opus 5 | $0.00016 | $0.00756 |
| Sonnet 5 | $0.00006 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
bmad-teach-me-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 9d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- bmad-teach-me-testing — 100% identical, 0 lines differ
- bmad-teach-me-testing — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teach Me Testing — TEA Academy
Goal: Provide self-paced, multi-session learning that teaches testing fundamentals through advanced practices, scalable to entire teams without requiring instructor time.
Role: In addition to your name, communication_style, and persona, you are also a Master Test Architect and Teaching Guide collaborating with learners at all levels. This is a partnership, not a lecture. You bring expertise in TEA methodology, testing principles, and teaching pedagogy, while the learner brings their role context, experience, and learning goals. Work together to build their testing knowledge progressively.
Meta-Context: This workflow uses continuable architecture with state persistence across sessions. Users can pause and resume anytime, jump to any session based on experience, and learn at their own pace over 1-2 weeks.
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
Conventions
- Bare paths (e.g.
instructions.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.- Resolve sibling workflow files such as
instructions.md,checklist.md,steps-c/...,steps-e/...,steps-v/..., and templates from{skill-root}.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
What ships with it
27 files 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.
- checklist.md 5.5 KB
- customize.toml 1.5 KB
- data/curriculum.yaml 3.9 KB
- data/quiz-questions.yaml 8.2 KB
- data/role-paths.yaml 5.2 KB
- data/session-content-map.yaml 9.3 KB
- data/tea-resources-index.yaml 20 KB
- instructions.md 4.3 KB
- steps-c/step-01-init.md 6.3 KB
- steps-c/step-01b-continue.md 4.2 KB
- steps-c/step-02-assess.md 7.2 KB
- steps-c/step-03-session-menu.md 7.2 KB
- steps-c/step-04-session-01.md 15 KB
- steps-c/step-04-session-02.md 13 KB
- steps-c/step-04-session-03.md 7.4 KB
- steps-c/step-04-session-04.md 6.0 KB
- steps-c/step-04-session-05.md 5.7 KB
- steps-c/step-04-session-06.md 5.3 KB
- steps-c/step-04-session-07.md 6.9 KB
- steps-c/step-05-completion.md 9.7 KB
- steps-e/step-e-01-assess-workflow.md 3.3 KB
- steps-e/step-e-02-apply-edits.md 3.0 KB
- steps-v/step-v-01-validate.md 6.1 KB
- templates/certificate-template.md 2.4 KB
- templates/progress-template.yaml 2.2 KB
- templates/session-notes-template.md 1.0 KB
- workflow-plan-teach-me-testing.md 33 KB
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.
- 9d ago First seen · 130 lines · 32 tokens per session scan A ab9d67173dd7
bmad-teach-me-testing is a skill published in the GitHub repository marlonvidal/tech-manager-os (17 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 1,512 once invoked, about $0.0002 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
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
Vibe Coding Mastery
The complete operating system for building software with AI. From first prompt to production deployment — prompting frameworks, architecture patterns, testing strategies, debugging playbooks, and production graduation checklists. Works with Claude Code, Cursor, Windsurf, Copilot, and any AI coding tool.
workshop-testing
Walk through the .NET AI Workshop as an attendee to validate that the READMEs, commands, and code snapshots still work. USE FOR: testing the workshop, testing a specific Part, dry-running the labs, verifying a README against its snapshot, reconciling or refreshing code snapshots, producing a workshop test report. DO…
Automation Interview Prep
Prepare for SDET and automation interviews round by round, covering coding screens, framework design, API testing tasks, scenario questions, and STAR stories built from real testing work.
paperlab_exam_alignment
Check whether a PaperLab course book prepares students for the associated exercises and exams. Use this when a book has source folders with exams, exercise PDFs, review chapters, learning objectives, or end-of-chapter questions.
ship-feature
End-to-end feature delivery — implement a feature, verify builds/tests pass, open a fully-filled draft PR, then automatically push every feedback round and review iteration to the same PR. Use when the user asks to implement or build a feature, fix-and-ship a change, or iterate on an existing feature PR.