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 agentmods add commands/tpmjs/tpmjs/blocks-developgit clone --depth 1 https://github.com/tpmjs/tpmjsWhat 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 | $0.00010 | $0.00737 |
| Opus 5 | $0.00005 | $0.00368 |
| Sonnet 5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
blocks-develop scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://tpmjs.com/api/sync/keyword -H "Authorization: Bearer $CRON_SECRET" How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Help the user develop new tools for the TPMJS registry using the blocks CLI. This workflow covers defining tools in blocks.yml, implementing them with AI SDK v6, validating with the blocks CLI, and publishing to npm.
Development Workflow
1. Define Tool in blocks.yml
Add tool definition to packages/tools/official/blocks.yml:
blocks:
category.toolName:
type: utility
description: "Clear description for LLMs"
path: "tool-directory-name"
domain_rules:
- id: rule_name
description: "Implementation requirement"
inputs:
- name: paramName
type: string
description: "Parameter description"
outputs:
- name: result
type: ResultType
description: "Output description"
measures: [working_implementation, valid_output_structure, proper_error_handling, ai_sdk_compliance]
2. Create Package Structure
packages/tools/official/tool-name/
├── package.json # npm package with tpmjs field
├── tsconfig.json # Extends @tpmjs/tsconfig
├── tsup.config.ts # Build config
├── block.ts # REQUIRED by validator
├── index.ts # Re-export from src
└── src/index.ts # Main implementation
3. Implement with AI SDK v6
import { jsonSchema, tool } from 'ai';
export const myTool = tool({
description: 'Description for LLMs',
parameters: jsonSchema<InputType>({
type: 'object',
properties: { /* ... */ },
required: ['field1'],
}),
async execute(input): Promise<OutputType> {
// REAL implementation - no stubs
return result;
},
});
export default myTool;
4. Run Validation
cd packages/tools/official
pnpm blocks run tool-name # Validate single tool
pnpm blocks run tool-name --force # Force full validation
pnpm blocks run --all # Validate all tools
5. Build and Publish
pnpm build
npm publish --access public
# Trigger sync to tpmjs.com
source apps/web/.env.local
curl -X POST https://tpmjs.com/api/sync/keyword -H "Authorization: Bearer $CRON_SECRET"
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.
- 2d ago First seen · 103 lines · 10 tokens per session scan A dc15ce64fbbe
blocks-develop is a command published in the GitHub repository tpmjs/tpmjs (24 stars, last pushed 8d ago), licensed MIT. It adds 10 tokens to every session and 737 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.