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/freepeak/ktme/documentationnpx skills add FreePeak/ktme --skill documentationgit clone --depth 1 https://github.com/FreePeak/ktmeWhat 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.00013 | $0.03907 |
| Opus 5 | $0.00006 | $0.01954 |
| Sonnet 5 | $0.00003 | $0.00781 |
| Haiku 4.5 | $0.00001 | $0.00391 |
Grade A, and why
documentation 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 -H "Authorization: Bearer $TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 722 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Comprehensive guidelines for writing clear, maintainable, and useful documentation.
When to Use
Use this skill when:
- Writing README files
- Creating API documentation
- Writing user guides
- Documenting architecture decisions
- Creating inline code documentation
- Writing changelogs and release notes
Documentation Types
1. Code Documentation (Inline)
Purpose: Explain how code works to developers
Rust Documentation
/// Calculates the total price for a list of items.
///
/// # Arguments
///
/// * `items` - A slice of items to calculate the total for
///
/// # Returns
///
/// The total price as a floating-point number
///
/// # Examples
///
/// ```
/// let items = vec![
/// Item { name: "Widget", price: 10.0 },
/// Item { name: "Gadget", price: 20.0 },
/// ];
/// assert_eq!(calculate_total(&items), 30.0);
/// ```
///
/// # Panics
///
/// Panics if any item has a negative price.
pub fn calculate_total(items: &[Item]) -> f64 {
items.iter().map(|item| item.price).sum()
}
/// User entity representing a system user.
///
/// This struct stores basic user information and provides
/// methods for user management.
///
/// # Examples
///
/// ```
/// let user = User::new("[email protected]", "John Doe");
/// println!("User: {}", user.name);
/// ```
#[derive(Debug, Clone)]
pub struct User {
/// User's email address (unique identifier)
pub email: String,
/// User's display name
pub name: String,
/// Account creation timestamp
pub created_at: DateTime<Utc>,
}
// Module documentation
//! # My Crate
//!
//! `my_crate` is a collection of utilities for doing X, Y, and Z.
//!
//! ## Features
//!
//! - Feature A
//! - Feature B
//!
//! ## Quick Start
//!
//! ```rust
//! use my_crate::do_something;
//! do_something();
//! ```
TypeScript/JavaScript Documentation
/**
* Parses a configuration file and returns a validated config object.
*
* @param filePath - Path to the configuration file
* @param options - Optional parsing options
* @returns Promise resolving to the parsed configuration
* @throws {ConfigError} If the file cannot be read or parsed
*
* @example
* ```typescript
* const config = await parseConfig('./config.toml');
* console.log(config.database.url);
* ```
*/
export async function parseConfig(
filePath: string,
options?: ParseOptions
): Promise<Config> {
// Implementation
}
/**
* User role enum defining permission levels.
*/
export enum UserRole {
/** Can view content */
Viewer = 'viewer',
/** Can edit content */
Editor = 'editor',
/** Full access to all features */
Admin = 'admin',
}
/**
* Configuration options for the API client.
*
* @example
* ```typescript
* const options: ApiClientOptions = {
* baseUrl: 'https://api.example.com',
* timeout: 5000,
* retries: 3,
* };
* ```
*/
export interface ApiClientOptions {
/** Base URL for API requests */
baseUrl: string;
/** Request timeout in milliseconds */
timeout?: number;
/** Number of retry attempts for failed requests */
retries?: number;
}
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 · 722 lines · 13 tokens per session scan A 76b9ea21ca9f
documentation is a skill published in the GitHub repository FreePeak/ktme (15 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 3,907 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…