Borrowing it
Nothing to install: this file belongs to phuoctrung-ppt/ai-sdlc-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phuoctrung-ppt/ai-sdlc-workflow/master/.cursor/commands/tenant-context-check.mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/commands/phuoctrung-ppt/ai-sdlc-workflow/tenant-context-check)<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/tenant-context-check"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/tenant-context-check.svg" alt="Measured on agentmods" 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.00047 | $0.00277 |
| Opus 5 | $0.00023 | $0.00138 |
| Sonnet 5 | $0.00009 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
tenant-context-check 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 8d 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.
What it actually says
Domain example — this command is for multi-tenant projects that use
tenant_idcolumn isolation (see.cursor/rules/004-multi-tenancy-pattern.mdc). Skip this command if your project is single-tenant or uses a different isolation model. Adapt the checklist to matchAGENTS.md §5.
Audit tenant isolation for: {code_path}
Per .cursor/rules/004-multi-tenancy-pattern.mdc and AGENTS.md §5:
- All tenant-scoped tables have
tenant_id(or are explicitly marked as global) - Tenant guard applied on every tenant-scoped route
- Every query that touches tenant-scoped data filters by
tenant_id - No cross-tenant data leaks in API responses
- Global/shared entities (users, roles, etc.) have
tenant_idNULL or use a global flag perAGENTS.md §5 - Soft limits (quotas) return 403 with an appropriate upgrade/contact prompt
Output: PASS/FAIL with file:line issues.
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.
- 8d ago First seen · 22 lines · 47 tokens per session scan A f91a3b331e84
tenant-context-check is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 277 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.