Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Prompt file imported from albegali/agentic-portal (.cursor/commands/weekly.md). Copyright stays with the author.
/weekly
Project journal — weekly summary (minimal cost)
Recommended model: Claude Haiku 5.5 (tier fast, see models.toml). Switch to it before running this command.
Follow workflow/steps/weekly.md.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
<!-- Generated by tools/render_agents.py from workflow/workflow.toml and models.toml — do not edit; run `make agents`. -->
# /weekly
Project journal — weekly summary (minimal cost)
> Recommended model: **Claude Haiku 5.5** (tier `fast`, see models.toml). Switch to it before running this command.
Follow `workflow/steps/weekly.md`.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "<!-- Generated by tools/render_agents.py from workflow/workflow.toml and models.toml — do not edit; run `make agents`. -->\n# /weekly\n\nProject journal — weekly summary (minimal cost)\n\n> Recommended model: **Claude Haiku 5.5** (tier `fast`, see models.toml). Switch to it before running this command.\n\nFollow `workflow/steps/weekly.md`.",
"variables": [],
"notes": "Project journal — weekly summary (minimal cost)",
"metadata": {
"source": {
"provider": "github-cursor-commands",
"repository": "https://github.com/albegali/agentic-portal",
"path": ".cursor/commands/weekly.md",
"ref": "0694fcfa6f9f742ee5403ca5c19a53b6c55c6d0c",
"url": "https://github.com/albegali/agentic-portal/blob/0694fcfa6f9f742ee5403ca5c19a53b6c55c6d0c/.cursor/commands/weekly.md",
"key": "albegali/agentic-portal/.cursor/commands/weekly.md"
}
}
}
Installed into a catalogue, chosen by a router
Install weekly and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.