<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool-Calling on Singularity</title><link>https://singularity.sg/tags/tool-calling/</link><description>Recent content in Tool-Calling on Singularity</description><generator>Hugo</generator><language>en-SG</language><copyright>(c) {year} Abhishek Dujari</copyright><lastBuildDate>Sat, 15 Aug 2026 12:20:00 +0800</lastBuildDate><atom:link href="https://singularity.sg/tags/tool-calling/index.xml" rel="self" type="application/rss+xml"/><item><title>WarMachine: A Local Kali Linux Assistant for HTB and Pentesting</title><link>https://singularity.sg/2026/08/warmachine-local-kali-linux-assistant/</link><pubDate>Sat, 15 Aug 2026 12:20:00 +0800</pubDate><guid>https://singularity.sg/2026/08/warmachine-local-kali-linux-assistant/</guid><description>&lt;p&gt;&lt;a href="https://huggingface.co/ovedrive/WarMachine"&gt;WarMachine&lt;/a&gt; is my work-in-progress model for running a Kali Linux assistant locally. The current 4B version operates more like an OpenCode-compatible security assistant than a fully autonomous pentesting agent.&lt;/p&gt;
&lt;p&gt;I run it on a local GPU inside a sandbox for Hack The Box and other authorized pentesting work. It helps construct commands, runs them through structured tool calls, and uses the output to suggest what to try next. I find it most useful for code and command completion, especially when I know the objective but do not want to stop and reconstruct the exact syntax for each tool.&lt;/p&gt;</description></item></channel></rss>