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.
git clone --depth 1 https://github.com/WYZDevin/ChronoGeoLabWrote 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/commands/wyzdevin/chronogeolab/sync-tool)<a href="https://agentmods.dev/commands/wyzdevin/chronogeolab/sync-tool"><img src="https://agentmods.dev/badge/commands/wyzdevin/chronogeolab/sync-tool/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/commands/wyzdevin/chronogeolab/sync-tool"><img src="https://agentmods.dev/badge/commands/wyzdevin/chronogeolab/sync-tool.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.00000 | $0.01694 |
| Opus 5.5 | $0.00000 | $0.00678 |
| Sonnet 5.5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
sync-tool 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Tool Between Frontend and Backend
You are synchronizing a geospatial analysis tool between the frontend (app/front-end/) and backend (app/back-end/) codebases. The user will provide a tool name or ID, and optionally the direction.
Determine Direction
First, figure out where the tool currently exists:
- Check
app/back-end/app/tool_registry.pyfor backend registration - Check
app/front-end/src/tools/index.tsfor frontend registration - Check
app/back-end/app/tools/for the backend implementation file - Check
app/front-end/src/tools/for the frontend implementation file
Based on what exists:
- Tool exists only in backend → Register it in the frontend (stub only — no
analyze()implementation unless the user explicitly asks) - Tool exists only in frontend → Create a full backend implementation and register it
- Tool exists in both → Report that it's already synced, check if the tool IDs match across both sides
Direction A: Backend → Frontend (Registration Only)
When a tool exists in the backend but NOT in the frontend, create a frontend stub. This makes the tool visible in the UI and runnable via the backend, without implementing browser-side logic.
Steps
-
Read the backend tool to extract:
id,name,description,version,execution_policy, and whatoptions/attributesit accepts inexecute(). -
Create frontend tool file at
app/front-end/src/tools/<tool-name>-tool.ts:
import { SimpleTool, ToolOptionSchema } from '@/interfaces/simple-tool';
import { FeatureCollection } from '@/interfaces/data-interfaces';
import { AttributeMapping } from '@/interfaces/attribute-mapping';
export class <ToolClass> implements SimpleTool {
id = '<tool-id>'; // Must match backend tool.id exactly
name = '<Tool Name>';
description = '<description>';
icon = '<emoji>';
category = '<visualization|analysis|processing>' as const;
version = '<version>';
capabilities = {
executionPolicy: 'backend_only' as const, // Backend-only since no frontend implementation
};
// Only declare attributeMapping if the backend tool uses attributes
attributeMapping?: AttributeMapping = { /* match backend attributes */ };
getOptionSchema(): ToolOptionSchema[] {
// Mirror the options the backend tool accepts
return [ /* ... */ ];
}
async analyze(
data: FeatureCollection,
options: Record<string, unknown>,
attributes?: AttributeMapping
): Promise<FeatureCollection[]> {
// This tool runs on the backend only
throw new Error('<Tool Name> requires the backend server. Enable backend mode to use this tool.');
}
}
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.
- 2mo ago First seen · 168 lines · 0 tokens per session scan A daff98f06d33
sync-tool is a command published in the GitHub repository WYZDevin/ChronoGeoLab (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,694 tokens. 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.
sync-tool compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sync-toolWYZDevin/ChronoGeoLab | Command | 2 | 3mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |