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 pjt222/agent-almanac --skill analyze-tensegrity-systemgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/analyze-tensegrity-system)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/analyze-tensegrity-system"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/analyze-tensegrity-system/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/pjt222/agent-almanac/analyze-tensegrity-system"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/analyze-tensegrity-system.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.00094 | $0.05126 |
| Opus 5 | $0.00047 | $0.02563 |
| Sonnet 5 | $0.00019 | $0.01025 |
| Haiku 4.5 | $0.00009 | $0.00513 |
Grade A, and why
analyze-tensegrity-system 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Tensegrity System
Analyze a tensegrity (tensional integrity) system -- a structure where isolated compression elements (struts) are stabilized by a continuous tension network (cables/tendons). Determine the system's force balance, prestress equilibrium, structural stability, and cross-scale coherence from molecular cytoskeleton to architectural form.
When to Use
- Evaluating whether a structure exhibits true tensegrity (compression-tension separation) or is a conventional frame
- Analyzing the structural stability of a tensegrity design in architecture, robotics, or deployable structures
- Applying Donald Ingber's cellular tensegrity model to cytoskeletal mechanics (microtubules, actin, intermediate filaments)
- Assessing the load capacity and failure modes of an existing tensegrity system
- Determining whether a biological structure (cell, tissue, musculoskeletal system) can be modeled as tensegrity
- Computing prestress requirements for a tensegrity to achieve rigidity despite having more mechanisms than a conventional truss
Inputs
- Required: Description of the system (physical structure, biological cell, architectural model, or robotic mechanism)
- Required: Identification of candidate compression and tension elements
- Optional: Material properties (Young's modulus, cross-section, length for each element)
- Optional: External loads and boundary conditions
- Optional: Scale of interest (molecular, cellular, tissue, architectural)
- Optional: Known topology family (prism, octahedron, icosahedron, X-module)
Procedure
Step 1: Characterize the System
Establish the complete physical description by identifying every compression element (strut) and tension element (cable), their connectivity, and the boundary conditions.
- Compression inventory: List all struts -- rigid elements that resist compression. Record each strut's length, cross-section, material, and Young's modulus. In biological systems, identify microtubules (hollow cylinders, ~25 nm outer diameter, 14 nm inner diameter, E ~ 1.2 GPa, persistence length ~ 5 mm).
- Tension inventory: List all cables -- elements that resist tension only and go slack under compression. Record rest length, cross-sectional area, and tensile stiffness. In biological systems: actin filaments (helical, ~7 nm diameter, E ~ 2.6 GPa, persistence length ~ 17 um) and intermediate filaments (IFs, ~10 nm diameter, highly extensible, strain-stiffening).
- Connectivity topology: Document which struts connect to which cables at which nodes (joints). Construct the incidence matrix C (rows = members, columns = nodes) encoding the topology.
- Boundary conditions: Identify fixed nodes (grounded joints), free nodes, and external loads. Note gravitational loading direction and magnitude.
- Scale identification: Classify as molecular (nm), cellular (um), architectural (m), or robotic (cm-m).
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 · 265 lines · 94 tokens per session scan A d1e214df85f7
analyze-tensegrity-system is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 5,126 once invoked, about $0.0005 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
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".