What is spera-build-module?

A tool for creating and changing reusable Spera graph modules. A graph module is a group of connected processing steps with defined inputs and outputs.

Use it to create, edit, fork, repair, compile, or configure reusable modules in Spera.

It checks that the module's connections and input/output contract are valid before treating the module as complete. It also supports repairing an existing module in place.

spera-build-module — Skill for Claude Code by praveenmanikandan

Install

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.

Any agent

npx skills add praveenmanikandan/spera-cursor-plugin --skill spera-build-module

Clone the repo

git clone --depth 1 https://github.com/praveenmanikandan/spera-cursor-plugin

Made for: Claude Code.

Or install spera, the plugin that ships this one along with the rest of its 8 skills, 2 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module/github.svg)](https://agentmods.dev/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module)

Your own site

<a href="https://agentmods.dev/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module"><img src="https://agentmods.dev/badge/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module"><img src="https://agentmods.dev/badge/skills/praveenmanikandan/spera-cursor-plugin/spera-build-module.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 599 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00081	$0.00599
Opus 5	$0.00041	$0.00300
Sonnet 5	$0.00016	$0.00120
Haiku 4.5	$0.00008	$0.00060

Measured 8d ago against content hash 7e68fffab00d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

spera-build-module 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.

skills/spera-build-module/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build a Spera module

Read and follow spera-foundations first. A module is complete only after its graph compiles and its exact input/output contract is persisted.

Build or edit

Call spera_context_get for the exact project and retain workflowId plus stateToken.
Read the compact node catalog, then batch exact details only for selected node types.
For an edit, resolve and read one exact module ID. If projectIds contains multiple projects, pass the intended project to spera_artifact_get; use its returned projectId and current revision for every mutation. If it is read-only, fork only when the user asked to edit it and continue on the returned owned ID.
Call spera_module_create or spera_module_patch with the minimum graph operations and a fresh idempotency key. Every add_node payload includes id, type, category, and config; every add_edge payload includes id, source, target, and exact catalog port handles when wiring.
Repair validation or compile diagnostics in place exactly as directed. A validation correction uses the returned state token and a fresh idempotency key; only a byte-identical replay reuses the original key. Never recreate the module or consume retries on a repeated byte-equivalent patch.

Configure ports and finish

Continue only when the graph result is compile-clean and explicitly allows spera_module_ports_set.
Send the complete input and output arrays against the exact compiled module revision. Every output must name an existing internal node and exact output handle; every fallback node must exist.
On a stale revision, refresh rather than overwrite. On invalid ports, correct only the named port.
Stop at the terminal result. Retain its complete artifact.moduleReference and port arrays as the only supported strategy-embedding contract. moduleReference is ready to copy into a module node's config; its moduleVersion is the semantic/draft version, not the artifact revision or commit ID. Report the owned module ID, module version, final revision, and verified compile receipt.

Read the full file on GitHub · 40 lines

Changes

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 · 40 lines · 81 tokens per session scan A 7e68fffab00d

Subscribe to this mod's changes

spera-build-module is a skill published in the GitHub repository praveenmanikandan/spera-cursor-plugin (0 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 599 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.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens