Borrowing it
Nothing to install: this file belongs to rhll07/wealvest-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rhll07/wealvest-ai/main/.agents/skills/tools-resources-prompts/SKILL.mdgit clone --depth 1 https://github.com/rhll07/wealvest-aiWrote 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/rhll07/wealvest-ai/tools-resources-prompts)<a href="https://agentmods.dev/skills/rhll07/wealvest-ai/tools-resources-prompts"><img src="https://agentmods.dev/badge/skills/rhll07/wealvest-ai/tools-resources-prompts/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/rhll07/wealvest-ai/tools-resources-prompts"><img src="https://agentmods.dev/badge/skills/rhll07/wealvest-ai/tools-resources-prompts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00048 | $0.02316 |
| Opus 5 | $0.00024 | $0.01158 |
| Sonnet 5 | $0.00010 | $0.00463 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade A, and why
nitrostack-tools-resources-prompts 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 10d 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
100% identical to nitrostack-tools-resources-prompts — 0 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill whenever you are defining, editing, or validating tools, resources, or prompts on a NitroStack MCP server.
Defining Tools with @Tool
An MCP tool exposes a function that an AI client can invoke. Decorate a service or controller method with @Tool.
Key Tool Options:
name: Kebab-case or snake_case unique identifier.description: Detailed description explaining when and how the client should use it.inputSchema: A Zod object schema for strict validation of inputs.outputSchema(optional): Zod schema validating the output structure.
import { ToolDecorator as Tool, ControllerDecorator as Controller, InitialTool, z, ExecutionContext } from '@nitrostack/core';
@Controller('weather')
export class WeatherService {
@Tool({
name: 'get_current_weather',
description: 'Get the current weather forecast for a specific city.',
inputSchema: z.object({
city: z.string().describe('The name of the city, e.g., San Francisco'),
unit: z.enum(['celsius', 'fahrenheit']).default('celsius'),
}),
})
@InitialTool() // Auto-invoked when the AI client initializes/starts
async getWeather(
input: { city: string; unit: 'celsius' | 'fahrenheit' },
ctx: ExecutionContext
) {
ctx.logger.info(`Fetching weather for ${input.city}`);
// implementation
return {
city: input.city,
temp: 22,
condition: 'Sunny',
};
}
}
Defining Resources with @Resource
An MCP resource exposes static or dynamic data files/URIs that the AI client can read.
Key Resource Options:
uri: URI pattern (e.g.,git://{owner}/{repo}/fileor staticapp://config).name: Unique name of the resource.description: Explanation of what data this resource provides.mimeType: Mime type of the response (e.g.,text/plain,application/json).
import { Resource, ExecutionContext } from '@nitrostack/core';
export class ConfigResources {
@Resource({
uri: 'app://settings',
name: 'Application Settings',
description: 'System-wide configuration settings and parameters.',
mimeType: 'application/json',
})
async getSettings(ctx: ExecutionContext) {
return {
environment: 'development',
debugMode: true,
};
}
}
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.
- 10d ago First seen · 288 lines · 48 tokens per session scan A 6afc492e781b
nitrostack-tools-resources-prompts is a skill published in the GitHub repository rhll07/wealvest-ai (0 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 2,316 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to nitrostack-tools-resources-prompts, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
i18n-parity
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change…
dag-map
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.
history-portability
Import Claude Code or Codex history and move complete CCAM datasets between machines. Use when rescanning provider history, importing a copied directory, uploading JSONL or archives, exporting a backup, restoring it idempotently, or verifying that tokens, workflows, runs, rules, and pricing survived.
alert-management
Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.
remote-collection
Configure and troubleshoot CCAM Remote Data Sources that collect Claude Code and Codex history over SSH. Use when adding, editing, testing, syncing, or removing a remote machine, verifying provider paths, or deciding whether to retain or purge imported sessions.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.