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 pantheon-org/tekhne --skill workspace-patternsgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/workspace-patterns)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/workspace-patterns"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/workspace-patterns/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/pantheon-org/tekhne/workspace-patterns"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/workspace-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01238 |
| Opus 5 | $0.00028 | $0.00619 |
| Sonnet 5 | $0.00011 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
nx-workspace-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Workspace Patterns
Navigation hub for Nx workspace architecture and operations.
When to Use
- You are structuring or refactoring an Nx monorepo.
- You need dependency boundaries enforced by tags and lint rules.
- You need reliable affected-command CI and caching performance.
When Not to Use
- The repository is single-project with no monorepo coordination needs.
- The task is framework-specific build setup unrelated to Nx graph and task orchestration.
Workflow
- Structure workspace domains (
apps/,libs/,tools/). - Define tags and project graph conventions.
- Configure target pipelines and caching defaults.
- Enforce module boundaries and verify violations fail with
nx lint --skip-nx-cache. - Integrate affected commands in CI with explicit base/head strategy.
Constraint Guidelines
Hard Constraints
- MUST tag projects consistently for scope/type-based constraints.
- MUST configure
targetDefaultsfor build/test/lint dependency flow. - MUST use affected commands in CI for scalable execution.
Flexible Choices
- CAN choose tag vocabulary (
scope:*,type:*,platform:*) if consistent. - CAN choose cache backend (Nx Cloud or self-hosted) by org constraints.
- CAN choose library granularity based on team ownership and release cadence.
Fallback Behaviors
| Missing Config | Fallback |
|---|---|
| no explicit tags | allow broad deps temporarily with warning and migration plan |
| no target defaults | tasks run independently with reduced optimization |
| no CI base/head | default to main branch and document tradeoff |
Quick Commands
nx graph
nx affected -t lint,test,build --base=origin/main --parallel=3
nx show project my-app --web
nx reset
rg -n "@nx/enforce-module-boundaries|depConstraints" .
Configuration Examples
nx.json targetDefaults
{
"targetDefaults": {
"build": {
"dependsOn": ["^build"],
"inputs": ["production", "^production"],
"cache": true
},
"test": {
"dependsOn": ["build"],
"inputs": ["default", "^production", "{workspaceRoot}/jest.preset.js"],
"cache": true
},
"lint": {
"inputs": ["default", "{workspaceRoot}/.eslintrc.json"],
"cache": true
}
}
}
What ships with it
23 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.
- .audits/2026-02-21/analysis.md 8.2 KB
- .audits/2026-02-21/audit.json 146 B
- .audits/2026-02-21/remediation-plan.md 238 B
- .audits/2026-02-22/analysis.md 8.2 KB
- .audits/2026-02-22/audit.json 146 B
- .audits/2026-02-22/remediation-plan.md 238 B
- .audits/2026-02-23/analysis.md 8.2 KB
- .audits/2026-02-23/audit.json 147 B
- .audits/2026-02-23/remediation-plan.md 234 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 420 B
- .audits/2026-03-02/remediation-plan.md 2.5 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 439 B
- CHANGELOG.md 736 B
- evals/scenario-01.md 3.1 KB
- evals/scenario-02.md 3.6 KB
- evals/scenario-03.md 3.6 KB
- evals/scenario-04.md 2.8 KB
- references/affected-commands.md 777 B
- references/caching-strategies.md 804 B
- references/project-boundaries.md 751 B
- references/project-graph-configuration.md 792 B
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 · 177 lines · 55 tokens per session scan A 1d1d833b25b4
nx-workspace-patterns is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,238 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
nx-workspace
Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT…
azure-devops
Expert knowledge for Azure DevOps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing agent pools, work item processes, analytics/OData reports, org limits, or…
google-cloud-slo-alert-configuration
Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.