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 skills/tari-project/tari-ootle/github-copilotnpx skills add tari-project/tari-ootle --skill github-copilotgit clone --depth 1 https://github.com/tari-project/tari-ootleWhat 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.00016 | $0.11940 |
| Opus 5 | $0.00008 | $0.05970 |
| Sonnet 5 | $0.00003 | $0.02388 |
| Haiku 4.5 | $0.00002 | $0.01194 |
Grade A, and why
github-copilot 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 3d 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.
This is a copy
97% identical to aider — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are assisting with development on the Tari Ootle platform — a decentralized application layer built on Tari L2. Templates (smart contracts) are written in Rust, compiled to WASM (wasm32-unknown-unknown), and deployed to the network.
Overview
Tari Ootle is a decentralized application platform built on the Tari Layer 2 network. You build templates (smart contracts) in Rust, compile them to WASM (wasm32-unknown-unknown), publish them to the network, and interact with deployed components (instances of templates) via transactions.
Key concepts:
- Template — A Rust module annotated with
#[template]that defines the logic and state structure. Compiled to WASM and deployed to the network. - Component — A live instance of a template on-chain. Holds state (struct fields) and exposes public methods.
- Resource — A native digital asset (fungible token or non-fungible NFT). Created with
ResourceBuilder. Cannot be copied or accidentally destroyed. - Vault — An on-chain container that holds exactly one type of resource. Must be stored in a component before the function returns.
- Bucket — A temporary container for resources during a transaction. Used to move assets between vaults or to/from method calls.
- Transaction — A set of instructions (CallFunction, CallMethod, etc.) that are signed, submitted, and executed atomically.
Crate ecosystem:
| Crate | Purpose | Used In |
|---|---|---|
tari_template_lib |
Core template library: prelude, ResourceBuilder, Vault, Bucket, ComponentManager, CallerContext, emit_event, rand, macros (args!, rule!, metadata!) |
Templates (WASM) |
tari_template_lib_types |
Shared types: Amount, ComponentAddress, ResourceAddress, NonFungibleId, AccessRule, OwnerRule, Metadata |
Templates & client |
tari_ootle_transaction |
TransactionBuilder and args! macro for constructing transactions |
Client & tests |
ootle-rs |
Client wallet and Indexer provider: sign, submit, watch transactions; builtin template helpers (faucet) | Client apps |
tari_template_test_tooling |
Local test harness (dev-dependency): compile templates to WASM and run against the engine in-process | Tests only |
Important macro distinction:
args!(fromtari_template_lib::prelude) — used inside templates for cross-template calls (alias forinvoke_args!)args!(fromtari_ootle_transaction) — used in test code and client code forTransactionBuilder,TemplateTest::call_function, andcall_method. ProducesVec<NamedArg>.
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.
- 3d ago First seen · 1,267 lines · 16 tokens per session scan A cb8048076eb8
github-copilot is a skill published in the GitHub repository tari-project/tari-ootle (28 stars, last pushed 6d ago), licensed BSD-3-Clause. It adds 16 tokens to every session and 11,940 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to aider, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
bitfence
Fetch a pre-transaction risk score and advisory recommendation for tokens on Solana, Base, Ethereum, Arbitrum, BSC, and HyperEVM before the user trades, swaps, or provides liquidity. Read-only; never signs or moves funds.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
ansem-crypto
Use when evaluating crypto narratives, attention rotation, memecoin cycles, Solana-style ecosystem momentum, social distribution, and reflexive retail flows in an Ansem-style crypto market framework.
copy-trading-solana
Copy trade Solana wallets - mirror trades automatically.
[REPLACE: SKILL_NAME]
Price and volume tracker for [REPLACE: TOKENSYMBOL] with anomaly alerts above [REPLACE: ALERTTHRESHOLDPCT]% movement.
kraken-order-types
Complete reference for all spot and futures order types and modifiers.