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 narpatsinghpurohit/tstack --skill permission-guidelinesgit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/permission-guidelines)<a href="https://agentmods.dev/skills/narpatsinghpurohit/tstack/permission-guidelines"><img src="https://agentmods.dev/badge/skills/narpatsinghpurohit/tstack/permission-guidelines.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.00085 | $0.01103 |
| Opus 5 | $0.00043 | $0.00551 |
| Sonnet 5 | $0.00017 | $0.00221 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
permission-guidelines 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 7d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Permission Guidelines
Two-Level RBAC Model
tstack uses a two-level permission system inspired by Laravel Jetstream's team model:
Platform Level (User document)
User.roleNames → expand via Role.permissionNames
+ User.directPermissions → explicit grants
- User.revokedPermissions → explicit denials
= platformPermissions
Tenant Level (Membership document)
Membership.roleNames → expand via Role.permissionNames
+ Membership.directPermissions → explicit grants
- Membership.revokedPermissions → explicit denials
= tenantPermissions
JWT Contains
[...new Set([...platformPermissions, ...tenantPermissions])]
Merged union for the user's currentOrgId. Changes when user switches org.
Permission Format
Dot notation: resource.action (e.g., products.create, access.superadminSurface)
Never colon notation. Always lowercase resource, camelCase for multi-word actions.
Default Roles
| Role | Level | Purpose |
|---|---|---|
| Superadmin | Platform | Full platform access, manage all orgs/users/roles |
| Admin | Org | Full org access, manage members/invitations |
| Member | Org | Basic org access, read-only by default |
Quick Workflow
- [ ] Step 1: Decide whether to reuse or add permissions
- [ ] Step 2: Update shared permission definitions
- [ ] Step 3: Protect backend endpoints with @Can/@CanAny + orgId scoping
- [ ] Step 4: Gate frontend routes, entry points, and actions with useCan()
- [ ] Step 5: Review backend/frontend permission alignment
Step 1: Reuse vs Add
Inspect existing catalog in packages/shared/src/constants/permissions.ts. Prefer CRUD pattern: resource.create, resource.view, resource.update, resource.delete.
Step 2: Update Shared Definitions
Add to PERMISSIONS object in packages/shared/src/constants/permissions.ts. Then run bun seed to sync to database.
Step 3: Protect Backend Access
@Can(PERMISSIONS.X)— requires ALL listed permissions (AND logic)@CanAny(PERMISSIONS.X, PERMISSIONS.Y)— requires ANY one (OR logic)@CurrentUser()→ passuser.orgId!into services- All queries go through
BaseRepositorywhich auto-scopes byorgId
What ships with it
6 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.
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.
- 7d ago First seen · 135 lines · 85 tokens per session scan A c70083124999
permission-guidelines is a skill published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 1,103 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…